We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 509
    • 93 Posts
    Hello,

    I did the update yesterday without problem and I discover this morning that the meta keywords are no more available in my page where I defined it. Also I don’t see when editing a ressource the old tabulation "Keywords" where we say the meta tags we want to add in this ressource.

    I did a quick search without success. What have been change here?

    I noticed also when I select the second tabulation with the publication option, the content is no more displayed under. Is that normal or do I have a problem ?

    Thanks in advance
      • 25663 MODX Staff
      • 12,272 Posts
      In the site configuration, you can turn back on the Meta Keywords management option for each Resource. This is deprecated and will be removed in the future though; TVs are a much better way to handle site meta content.
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 509
        • 93 Posts
        Thanks rtrash !
        Is there a documentation to explain to that through TV?
          • 4041
          • 788 Posts
          In it’s simplest implementation, you basically create a TV to hold the meta info you require.

          Create a TV (for this example it’s named "Meta_Keywords")

          Input type: Text (or Textarea)
          Default Value:(comma seperated list of your keywords used as default) Stuff,More Stuff,Stuff2

          Make sure you check the templates which this TV is allowed access to.

          Add this to the top of your template: <meta name="keywords" content="[*Meta_Keywords*]"/>

          Now for each document which uses the template you checked, there will be a text input TV named Meta_Keywords (which will be filled with the default content if you provided any) which can be edited on a per document basis.

          You can get alot fancier, but this should give you a start point smiley
            xforum
            http://frsbuilders.net (under construction) forum for evolution
            • 25663 MODX Staff
            • 12,272 Posts
            I’ll add a significant point to that excellent overview (thanks Breezer!): Make the default value of any "meta info TV" include something like the following. E.g., for meta descriptions the default value for the MODx site itself might look like:
            @INHERIT MODx is a popular and growing Open Source Content Management System / application framework using PHP and MySQL. It gives developers 100% control over their content, Manager interface and site structure, and is fast and easy to template using plain HTML.


            Why do this? You’re always ensured to have a meta description for every page, even if you don’t maually set one. Also, if you set a meta description tag for an entire branch of your site, it will get those for all child docs thanks to the @INHERIT binding. You can quickly stub out an acceptable set of meta descriptions for an entire site by crafting a reasonably generic default fallback, then hitting all the important top-level Container Resources in your Site Tree.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 509
              • 93 Posts
              Hi all,

              Thanks for your answers.
              I didn’t know @INHERIT. I have to learn about it...

              Personally I use Meta tags on my home page. And based on that, I think that the old solution was a lighter one instead of creating this TV for all documents, else I have to create maybe a specific template for my home page.
                • 25663 MODX Staff
                • 12,272 Posts
                Not at all. You can have empty TV values, and use PHx to test/omit the insertion if there’s none present if you prefer.

                The built-in Meta Keywords and Meta Tags management will be going away in the future—they’re deprecated. It’s simply not a good way to handle things, so be aware that in a future version you’ll almost certainly be blocked from upgrades if you want to maintain this functionality.
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me