Theme becomes spontaneously disabled

Okay, that's strange. If you're not seeing it with any other theme, then let's assume that it's fusion/prosper.

Some questions:

What is your administration theme setting?

Do you let your users choose different themes from their profile?

Are you using the Switchtheme module?

You said that the issue results in no default theme being set. So, even Garland is not set as the default theme?

Is the disabling happening after a fixed interval, or just after some variable amount of time?

What other themes/modules do you have enabled?

Anything unique/unusual about your setup?

Does it happen on both development (e.g., desktop) and production (e.g., server) systems?

Thanks for your feedback!

Christian,

Also, I recently added a check for the Fusion Core base theme in Acquia Prosper's template.php (in the acquia_prosper_preprocess() function). I added it to prevent Drupal from crashing if Prosper was installed, but Fusion wasn't. If it doesn't see Fusion Core, then it resets the theme back to Garland. This might be the source of the problem.

As long as you have Fusion Core installed and enabled, could you try commenting out the code in that function (or removing the function entirely) and seeing if you still get spontaneous disabling?

Thanks

I have this happen whenever I upgrade fusion core. I haven't noticed it at any other time and it's pretty noticeable because disabling the default theme totally crashes Advanced Forum. I lost a couple hours trying to track down what I thought was a bug in CTools but turned out to be my site theme getting disabled. :(

Michelle

After reading #2 i believe this is related to why my themes get disabled in the post here http://drupal.org/node/567962
Basically after some amount of time, usually pretty short for me all the themes are disabled (in my case i only had fusion/prosper enabled). But after this my theme did not move to garland. So Its seeming that this might be a bug in fusion. When it somehow gets disabled, prosper sees that it isn't enabled and says "uh-oh i better get disabled so i don't cause any problems" and it does so. I'm just not sure about the difference on that my theme isn't reverting to garland but is staying on prosper.

As for the questions in #1;
- i have no theme related modules.
- my admin theme is set to site default.
- Users dont get their own theme.
- Prosper is still marked as default, just disabled (my problem was that it was removing the skinr block options).
- Only prosper/fusion are enabled.
- Time seems random but usually within 10 minutes or so.
- The only other odd thing off is that im using pressflow drupal. but should be 100% backwards compatible (removed php4 support and performance boosts for php5, et al.)

Just my 2cents

It's still not happening just spontaneously for me, but I had it happen in a new place: administering blocks. I made a few changes, submitted the blocks page, went back to the forum page, and got the error again that's caused by the theme being disabled. I never had this problem before installing Fusion so it seems likely it's the cause.

Michelle

subscribing

Reading #7, it sounds like my issue is a little different. In my case, I have a custom Fusion subtheme set as default and also enabled. No other themes are enabled. When the issue happens, my subtheme becomes disabled but still remains as the default theme (the radio button is still correct, just the checkbox unchecks). Because of the core bug that allows default themes to be disabled and still work, I only notice it when I go to the forums because that bug crashes AF.

Michelle

I have same issue after updating to both skinr and prosper 3 sept. dev version.
O_o

Christian, et. al,

I haven't been able to reproduce this behavior yet, but if commenting out the preprocess code results in no disabling, then I'm assuming that's the problem.

In anticipation of that being the problem, I've attached a patch that detects the presence of the base theme using a different method (looking for it in the list of current themes, rather than checking for a function it provides).

No guarantees that this will fix it, but if people are willing to try it and let me know if it helps, I'd be very appreciative. This is one of those issues that will have to be resolved before we release the beta.

Thanks.

P.S., Michelle, I know that your bug sounds different--and it very likely is--but if you could give the patch a shot and let me know if it makes a difference or not, then I'll be better equipped to attack your issue (which may need to be filed separately).

I was experiencing this problem in a testing environment and then moved this theme to a live website (Yin Yang House). I could fairly reliably reproduce the bug by just viewing the themes page and the theme would be disabled. I put in the patch and that seemed better (or at least hasn't happened yet) but during one period last evening the site reverted to garland for no reason (it's only been live for half a day or so). I'll watch it more closely, but I'm skeptical that the fix is 100%... Has it worked well for anyone else?

No, patch don't work for me.
I see that my issue a little different.
My site theme not always switch to Garland.

@sociotech: I feel a little silly... I found this issue while I was reading the global tracker and somehow completely managed to miss it was for Acquia Prosper. The problem I have is with Fusion itself. I just have Fusion and my site's theme, which is a subtheme of Fusion. Sorry about that.

Michelle

The patch doesn't appear to work for me either. If I edit a block, the theme defaults to garland...

I removed the entire function and it seems better, but it still disables itself most of the time when I do an update (i.e. run update.php) or just look at the themes page (fusion core is also disabled at those points). And, I don't know if it's related because the error doesn't make much sense to me but I'm also seeing thousands of errors like below and it's (I believe) crashing my site at this point every few hours - oddly enough they all are referrer links from aggregator??

Type	php
Date	Sunday, September 13, 2009 - 8:21pm
User	xxx
Location	http://www.site.com/aggregator/categories/3/index_14ABECB3_8A8058C2_A78DE985.htm
Referrer	http://www.site.com/aggregator/categories/3
Message	Duplicate entry 'sites/all/themes/acquia_prosper/acquia_prosper.info' for key 1 query: INSERT INTO system (name, owner, info, type, filename, status, throttle, bootstrap) VALUES ('acquia_prosper', 'themes/engines/phptemplate/phptemplate.engine', 'a:16:{s:4:\"name\";s:14:\"Acquia Prosper\";s:11:\"description\";s:424:\"<a href=\"http://www.acquia.com\">Acquia\'s</a> Prosper is a grid-enabled Drupal 6 theme designed for e-commerce with <a href=\"http://www.ubercart.org\">Ubercart</a>. It requires the <a href=\"http://drupal.org/project/fusion\">Fusion Core</a> base theme and <a href=\"http://drupal.org/project/skinr\">Skinr</a> module for its advanced point-and-click theming features. By <a href=\"http://www.topnotchthemes.com\">TopNotchThemes</a>\";s:10:\"base theme\";s:11:\"fusion_core\";s:4:\"core\";s:3:\"6.x\";s:6:\"engine\";s:11:\"phptemplate\";s:11:\"stylesheets\";a:1:{s:3:\"all\";a:1:{s:28:\"css/acquia-prosper-style.css\";s:60:\"sites/all/themes/acquia_prosper/css/acquia-prosper-style.css\";}}s:7:\"scripts\";a:2:{s:19:\"js/jquery.corner.js\";s:51:\"sites/all/themes/acquia_prosper/js/jquery.corner.js\";s:27:\"js/acquia-prosper-script.js\";s:59:\"sites/all/themes/acquia_prosper/js/acquia-prosper-script.js\";}s:7:\"regions\";a:13:{s:13:\"sidebar_first\";s:13:\"sidebar first\";s:12:\"sidebar_last\";s:12:\"sidebar last\";s:10:\"header_top\";s:10:\"header top\";s:6:\"header\";s:6:\"header\";s:11:\"preface_top\";s:11:\"preface top\";s:14:\"preface_bottom\";s:14:\"preface bottom\";s:11:\"content_top\";s:11:\"content top\";s:7:\"content\";s:7:\"content\";s:14:\"content_bottom\";s:14:\"content bottom\";s:14:\"postscript_top\";s:14:\"postscript top\";s:17:\"postscript_bottom\";s:17:\"postscript bottom\";s:6:\"footer\";s:6:\"footer\";s:11:\"node_bottom\";s:11:\"node bottom\";}s:8:\"features\";a:9:{i:0;s:4:\"logo\";i:1;s:4:\"name\";i:2;s:6:\"slogan\";i:3;s:17:\"node_user_picture\";i:4;s:20:\"comment_user_picture\";i:5;s:6:\"search\";i:6;s:7:\"favicon\";i:7;s:13:\"primary_links\";i:8;s:15:\"secondary_links\";}s:8:\"settings\";a:3:{s:14:\"base-font-size\";s:12:\"font-size-12\";s:19:\"sidebar-first-width\";s:1:\"3\";s:18:\"sidebar-last-width\";s:1:\"3\";}s:5:\"skinr\";a:3:{s:7:\"options\";a:1:{s:13:\"inherit_skins\";b:1;}s:22:\"prosper-general-styles\";a:4:{s:5:\"title\";s:37:\"Acquia Prosper - general theme styles\";s:4:\"type\";s:6:\"radios\";s:11:\"description\";s:68:\"Acquia Prosper\'s styles for blocks, panels, views, and content types\";s:7:\"options\";a:10:{i:1;a:2:{s:5:\"label\";s:48:\"Gray rounded title background, plain white block\";s:5:\"class\";s:48:\"prosper-gray-rounded-plain prosper-rounded-title\";}i:2;a:2:{s:5:\"label\";s:43:\"Gray rounded title background, list styling\";s:5:\"class\";s:48:\"prosper-gray-rounded-style prosper-rounded-title\";}i:3;a:2:{s:5:\"label\";s:30:\"Rounded corner dark background\";s:5:\"class\";s:33:\"prosper-grayborder-darkbackground\";}i:4;a:2:{s:5:\"label\";s:32:\"Light gray background and border\";s:5:\"class\";s:34:\"prosper-lightgraybackground-border\";}i:5;a:2:{s:5:\"label\";s:41:\"Medium gray background with bottom border\";s:5:\"class\";s:41:\"prosper-mediumgraybackground-bottomborder\";}i:6;a:2:{s:5:\"label\";s:49:\"Gradient background with padding and thick border\";s:5:\"class\";s:23:\"prosper-gradient-border\";}i:7;a:2:{s:5:\"label\";s:9:\"Menu list\";s:5:\"class\";s:17:\"prosper-menu-list\";}i:8;a:2:{s:5:\"label\";s:32:\"Shopping cart - Light background\";s:5:\"class\";s:26:\"prosper-shoppingcart-light\";}i:9;a:2:{s:5:\"label\";s:31:\"Shopping cart - Dark background\";s:5:\"class\";s:25:\"prosper-shoppingcart-dark\";}i:10;a:2:{s:5:\"label\";s:50:\"Tabbed block - also set Quicktabs style to Default\";s:5:\"class\";s:17:\"prosper-quicktabs\";}}}s:16:\"prosper-comments\";a:3:{s:5:\"title\";s:30:\"Acquia Prosper: comment styles\";s:4:\"type\";s:6:\"radios\";s:7:\"options\";a:2:{i:1;a:2:{s:5:\"label\";s:43:\"Simple with white background and separators\";s:5:\"class\";s:22:\"prosper-comments-clean\";}i:2;a:2:{s:5:\"label\";s:32:\"Speech bubbles with pointed edge\";s:5:\"class\";s:21:\"prosper-comments-edgy\";}}}}s:7:\"version\";s:11:\"6.x-1.x-dev\";s:7:\"project\";s:14:\"acquia_prosper\";s:9:\"datestamp\";s:10:\"1252022451\";s:10:\"screenshot\";s:46:\"sites/all/themes/acquia_prosper/screenshot.png\";s:3:\"php\";s:5:\"4.3.5\";}', 'theme', 'sites/all/themes/acquia_prosper/acquia_prosper.info', 0, 0, 0) in /srv/yinyanghouse.com/public/modules/system/system.module on line 821.
Severity	error

Now that I've been seeing those errors - this all may have nothing to do with fusion or acquia prosper. It seems this is a pretty widespread problem with drupal 6 - http://drupal.org/node/307756

Okay, I've re-coded the way that acquia prosper calls fusion functions using Drupal theme() functions. This way, if the base theme (fusion) is missing, it'll just degrade gracefully, rather than throwing a WSOD. So now I've removed the code that switched to Garland altogether, thus preventing the default theme from ever being set to Garland.

I'll be updating the development snapshot with this fix soon after a bit more testing.

But the issue of fusion and acquia prosper disabling themselves is a separate issue. This still occurs after some period of time.

After a lot of troubleshooting, I found that disabling the Skinr module stopped the themes from being disabled.

I've posted my experiences in the Skinr issue queue (#581604: skinr disable the active theme), but I'd be interested in hearing if this also fixes the theme disabling for others here.

Looks like the Skinr folks have fixed this issue with their latest dev release: http://drupal.org/node/581604#comment-2091672

In addition, I've just committed the changes I mentioned above (that will prevent resetting to Garland) to Fusion Core and Acquia Prosper. The snapshots should be available tomorrow morning.

I saw this issue happen with a theme becoming disabled.. turns out the problem was two domains accessing the same database, but having different Drupal code bases in their own directories.. So one Drupal had the theme, the other didn't, and when you accessed it from the domain without the theme, it got disabled in the database.