Posted by kiamlaluno on November 6, 2008 at 1:50am
Jump to:
| Project: | Integrated Metatags |
| Version: | 6.x-1.0-beta5 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I need help to understand how to use the enable global settings.
From the code I can understand that a content type which inherits the global meta tags shows its meta tags (all its meta tags, including the global ones) only if the enable global option is selected.
This seems the opposite of what the description of that option says (If this is disabled, any content types that inherit these settings will also include these Metatags.).
Comments
#1
Great observation. It was initially designed to work as the field described, but a check in the nodeapi function will prevent tags from being displayed if the global tags are inherited but disabled.
Thinking about it, it may be more intuitive if I change it to simply not include the global tags if they're disabled, regardless if they're inherited. What do you think?
#2
The two different options placed in two different settings pages seem to be confusing, IMHO.
If they are disabled, I would expect they aren't used, even if they are inherited. Or that, or the enable global option is removed, and the global meta tag are used only in those content types which inherit them.
I would like better to see the first alternative, with the enable global option used to globally enable the default meta tags without to need to disable them in every content type settings.
#3
I've done this internally. I'll test it before I commit it. My plan is to get this tested in D5 and D6 (and PHP4) and will release the next beta once this is done.
#4
Are there any ideas when the next release will be made public?
#5
Sometime next week. With the American Thanksgiving Day this week, I'm a little busy with family. I'll make an effort early next week to try and get the next beta out.