By greg.b on

This only happens with my new zen sub theme.

I have the message- The theme registry has been rebuilt. Turn off this feature on production websites.

The same message is repeated twice.

ie
The theme registry has been rebuilt. Turn off this feature on production websites.
The theme registry has been rebuilt. Turn off this feature on production websites.

?How can I get rid of this message?

TIA :o)

⋅ Categories: Drupal 6.x

Comments

greg.b’s picture

greg.b commented

:o)
Seems you turn off that option in the themes config page.

The link on the warning just took me to my home page?

Was that a bug?

grendzy’s picture

grendzy commented

If the link to "Turn off" this feature isn't working, make sure you replaced STARTERKIT with your theme name in theme-settings.php.

see http://drupal.org/node/266407

BuyBub.com’s picture

BuyBub.com commented

This is the answer I've been looking for. I experienced the same problem with my installation of Zen, but now it's gone once I removed the STARTERKIT in my template files.

Thanks!
--
Antivirus Software made easy at Sytru.com

Bigbosspassion’s picture

Bigbosspassion commented

I was getting the same problem but replaced STARTERKIT with your theme name in theme-settings.php helped me out.
Thanks

ericdfields’s picture

ericdfields commented

Likewise. Thanks.

edanisko’s picture

edanisko commented

I would prefer to simply turn off the warning instead of the rebuild process.

can someone tell me how?

Thanks
Ed

gasm’s picture

gasm commented

A good idea!

bsimon’s picture

bsimon commented

http://drupal.org/node/322480

cloudmaker’s picture

cloudmaker commented

Go to the current Theme (Home › Administer › Site building › Themes ›) and if is a Zen sub theme then go to:
Theme development settings

Easy.

anrikun’s picture

anrikun commented

I have this message too.
My problem is I don't even know what it means.
So I don't even know why it has to be turned off :-)
Can you explain me?
Thanks

stefanhapper’s picture

stefanhapper commented

Where is "Theme Development Settings" ?

I am using ZEN sub theme and I have also looked if there is STARTERKIT still in theme-settings.php, but it isn't

bsimon’s picture

bsimon commented

go to the page cloudmaker described and click on configure next to the theme name - if the option exists for that theme, it will be at the bottom of the page

stefanhapper’s picture

stefanhapper commented

Where is "Theme Development Settings" ?

I am using ZEN sub theme and I have also looked if there is STARTERKIT still in theme-settings.php, but it isn't

(sorry, double, can't delete)

twirlingsky’s picture

twirlingsky commented

nevermind...answered my own question

gearhead’s picture

gearhead commented

When I Rebuild theme registry on every page and and then click save the changes will not save.

Any ideas?

yan’s picture

yan commented

I don't know if I'm dumb or blind, but I still can't find the "theme development settings" to turn off the theme registry rebuild. When I click on the link in the warning message, it takes me to admin/build/themes/settings/<theme>, but there isn't such an option. I'm using Zen, but I tried the same with Garland - no difference. Is this a bug or am I just stupid?

Edit: I am stupid. I was sure I had changed the STARTERKIT appearances in theme-settings.php, but I didn't double check. There were still appearances of STARTERKIT. Changing those made the config options come up.

jknapp’s picture

jknapp commented

It took me a while to dig this out...

The STARTERKIT.info file comes with the following (line 86): settings[zen_rebuild_registry] = 1

... so that hardcodes the rebuild to "Yes."

In your new theme or themes, check for that setting and disable it. Then go to the theme configuration of every one of your Zen sub-themes (including Zen) via
/admin/build/themes/settings page. [If you don't see a "configure" link to the right, you need to hit the checkbox to enable your theme, then save.]

Make sure each theme that has the "Theme-specific settings" group has the following option disabled. If it's checked, uncheck and save...

Theme development settings - Theme registry: [x] Rebuild theme rregistry on every page

After doing this. Go to Performance, /admin/settings/performance , and "Clear cache data"

This should solve the rebuild issue.

Note that a sub-theme also seems to run through the Zen sub-theme's template.theme-registry.inc on top of whatever sub-theme you create. So that's why you can end up seeing two rebuild warning messages (or more) at a time.

Hope this is useful. I just spent the last three hours digging to make the pain stop... :-/

ophie’s picture

ophie commented

this may or may not help anyone but I had this with acquia today. I went in, disabled, logged out, logged back in, and got the errors to go away after reselecting the theme. Go figure, but something wasn't being read correctly. Afterwards, I was able to turn off the caching

EmperorForearm’s picture

EmperorForearm commented

I had a similar issue. Tried the earlier fixes, and ended up reverting them, but once I disabled the custom theme I was using and re-enabled it I was able to turn off the registry rebuilding on the theme configuration page.

somatics’s picture

somatics commented

I was having this same problem today. Every time I went to /admin/build/themes/settings/theme_name and changed it to not rebuild the theme registry it would act like it was saving the settings; but I would continue to get the warning message and every time I went back to /admin/build/themes/settings/theme_name, it would have the original setting to rebuild (plus any other original settings I tried to change).

Here's how I fixed it:

I went to the folder on the server for the theme, where I found the theme's theme-settings.php file. I checked and found out it had Read permissions only for the www group (on Unix that's the group Apache2 webserver runs under to read/serve and write to files). I changed the permissions to Read & Write instead.

Then, when I went back to the /admin/build/themes/settings/theme_name page and changed the settings and saved them, it told me the configurations options were saved and they stayed saved!