Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.If you upgrade from 1.0 and you have configured your head and edit tags shown in your code or on node edit forms this settings are not kept after the upgrade. All this checkboxes are disabled after the upgrade. This need to be fixed for a smooth upgrade path.
PS: We should also change the fieldset title after #587070: Meta tags form fields are always shown in the administration pages even if they are not selected to appear in the edit forms to something more generic.
Comments
Comment #1
avpadernoI changed, and committed the code in CVS.
Comment #2
hass commentedWhat do you think about changing the fieldset titles to be more generic?
Comment #3
hass commentedBug is fixed.
Comment #4
avpadernoIf you have any suggestions, I will change it.
This needs another issue report; what do you think of . After that, and before version 6.x-1.3, strings should be frozen. Maybe the report could be used to review all the strings actually used in the user interface; in this way, the strings that needs to be changed would be changed all in once.
Comment #5
hass commentedYes, I already thought about a string freeze for translation, too. Shouldn't be many changes... let's try to do a quick review only - otherwise I think it would be much better to get a new stable release *out* - than holding it back for minor text changes only. I'm also fine with doing this later in 1.4 if it would hold the release back for longer than one or two days... a final should have higher priority - e.g. release tomorrow. I'm no longer aware about real blockers with data loss. Any remaining issues you are aware about that need to be fixed?
Comment #6
avpadernoThere was a report about the setting for the content types to use the node teaser that was reset to the value of the global setting. If that has been already fixed, then I don't know of any other issues.
I agree that the strings review has a lower priority, and it should not hold the next official release. It's fine with me if the strings review is postponed, but it will need to be done, later or soon.
Comment #7
avpadernoThe reported problem has been already resolved.
There is an issue that needs to be resolved (#601436: When the option "Repeat meta tags for lists" is not selected, the canonical URL is not used) before the official release 6.x-1.3 is released.