Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.hello,
I have Zen installed in /sites/all/themes
I have a copy of STARTERKIT in /sites/mysite/themes/MYTHEME a few days ago
today I got
Zen 6.x-1.x-dev (2008-Apr-22)
Recommended version: 6.x-1.x-dev (2008-May-02) * Download * Release notes
Includes: Zen based MyDemo
I downloaded the new dev archive and put in site/all/themes but the update status still shows me this message.
I guess this is related to the fact that the MYTHEME is still the old version. How can I get around this? Or, how can I update MYTHEME without loosing already made changes?
Yes, I understand that ZEN for drupal-6 is not yet released and therefore I can live with that behavior for now. but still ... perhaps something can be done ;)
Jens
Comments
Comment #1
Moonshine CreditAttribution: Moonshine commentedThe update status is keyed off the "datestamp" setting in your .info file for your subtheme. If it matches the latest datestamp for Zen then it will be shown as current.
So you can just update Zen, and then copy the datestamp value from Zen into your subtheme.info file. However, changes *are* taking place with Zen, so really you should look at what has been updated and see if it needs to be implemented in your subtheme. (IE. Changes made to the base starterkit, changes made to hooks you override, etc.)
Comment #2
JohnAlbinYes, drupal.org automatically adds a datestamp and version to the end of the .info files. Including the STARTERKIT.info file.
Looks like we need some documentation on this issue.
If you install the update_advanced module, you can configure update status to ignore your SUBTHEME when checking for updates.
Comment #3
JohnAlbinComment #4
dean.kwasniak CreditAttribution: dean.kwasniak commentedHi
This is something I am interested in as well. Can someone confirm that there is no requirement to update a sub-theme?
Cheers
Dean
Comment #5
JohnAlbinbetter title.
Comment #6
JohnAlbinJust had a brainwave on this. Since we have to rename the STARTERKIT.info file anyway… maybe I could rename the file to STARTERKIT.info.txt and just have the docs mention that you need to rename it to mythemename.info. That should prevent the auto-packaging script from adding the datestamp which triggers the bogus "out of date" warning. It would also prevent "STARTERKIT" from appearing in the list of Themes, which is really just clutter.
However, you would need to keep Zen active in order to be notified of Zen updates, I think.
I'll have to test this out in HEAD first.
Comment #7
JohnAlbinOk. So changing the STARTERKIT.info to STARTERKIT.info.txt does fix the bogus out of date messages.
BUT, it also prevents the update.module from listing available updates for Zen. So we would go from bogus update messages to no update messages. :-\
I might need to jump into the .info cache during a theme registry re-build and set the sub-theme's info to match Zen's info.
Comment #8
JohnAlbinOk, since update.module not displaying an update message is really a bug in core #456088: Sub-themes not notified of security updates for base themes, I think renaming STARTERKIT.info to STARTERKIT.info.txt is the way to go here.
Fixed in 6.x-2.x.
Comment #9
JohnAlbinFixed in 6.x-1.x-dev now too.
I've also updated the instructions in the README.txt and on How to build your own sub-theme (6.x).