Closed (works as designed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.13
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Feb 2012 at 23:25 UTC
Updated:
10 May 2012 at 04:00 UTC
Comments
Comment #1
damienmckennaThis is what the "meta tags creation options" block looks like on the main settings page: http://damienmckenna.com/post/18527548496
This is what the content type settings block looks like: http://damienmckenna.com/post/18527708319
Were you thinking of the latter rather than the former?
Comment #2
arianek commentedThe thing you're calling the "content type settings block" is definitely what I saw, but it was on /admin/content/nodewords at first - like on this other site (not the one this happened on) https://skitch.com/arianek/8gdfa/meta-tags-dalai-lama-center-for-peace-a... which is in 6.x-1.11
But I configured it on this new site which uses 6.x-1.13, and once I'd saved all the config for the main settings page /admin/content/nodewords and the Default and specific meta tags page /admin/content/nodewords/meta-tags, and the Frontpage settings, I went back to the main page and that fieldset was no longer there.
Comment #3
damienmckennaThanks for helping to find out what's going on. There's no trace of the string "Meta tags content generation options" in the current version - it was added in v6.x-1.10 and existed through v6.x-1.12 but disappeared during the cleanup that became 6.x-1.13. I will have to investigate this further.
Comment #4
damienmckennaComment #5
arianek commentedThat's SO STRANGE. I am 100% sure I configured the option... *digs for evidence*
OH SNAP. So, it would seem that I started working on this config Feb 27, and on Feb 28 security updates were done on this site! I must have had the tab open in my browser, not reloaded, configured, saved (with now the new version in place), and hence the disappearance?
Sneaky.
Comment #6
arianek commentedConfirmed, until the 28th it was using 6x-1.11.
Comment #7
damienmckennaA better title.
Comment #8
damienmckennaI went through the current options, and the content generation options were moved to each individual content type rather than being global.