I have installed Fusion Core along with Acquia Prosper and Skinr and Panels on http://learnbythedrop.com. I have been able to update the theme on the site but have noticed that the enabled checkbox will not stay checked for any of my modules located on the page at /admin/build/themes. I'm not 100% sure what other problems this is causing but for starters I'd like to get these boxes to stay checked.

Perhaps related, or not, is the fact that by database log has been filling up with errors since installing Fusion and Acquia Prosper. Here is a snippet of the very long php error.

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:385:\"<a href=\"http://www.acquia.com\">Acquia\'s</a> Prosper is grid-enabled and designed for <a href=\"http://www.ubercart.org\">Ubercart</a> e-commerce. It uses 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 easy point-and-click theming. 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:2:{s:28:\"css/acquia-prosper-style.css\";s:60:\"sites/all/themes/acquia_prosper/css/acquia-prosper-style.css\";s:26:\"design_packs/gray/gray.css\";s:58:\"sites/all/themes/acquia_prosper/design_packs/gray/gray.css\";}}s:7

There's a lot more to that error but hopefully it can give you some idea of the issue at hand. As I said I don't know if they are related but I'm posting it here just in case.

Rob Safuto
Awakened Voice

Comments

Anonymous’s picture

Anonymous (not verified) commented

After some more searching I see that this issue was being discussed at http://drupal.org/node/570624. The thread there says the issue should be fixed but I'm still experiencing the module checkboxes disappearing with all the latest releases installed. I have disabled the Skinr module and that seems to be fixed now. The long error mentioned above seems to be related. Someone else saw that issue (http://drupal.org/node/570624#comment-2037722) and I am no longer seeing those errors with Skinr disabled.

gooddesignusa’s picture

gooddesignusa commented

wow i thought i was going crazy. i've been getting tons of those errors. More so when using the views UI. I just checked my theme settings and you were right. They were unchecked.

subscribing

trevorleenc’s picture

trevorleenc commented

also having this problem.

started the other day when I upgraded to skinr 6.x-1.4 & fusion 6.x-1.0-rc1.

I've tried uninstalling the themes and modules, and no luck...can't seem to figure out what triggers this from happening either.

help :)

trevorleenc’s picture

trevorleenc commented

ok, I have backported to fusion-6.x-1.0-beta4 & skinr-6.x-1.3 and everything seems to be working.

not sure if this would be a fusion or a skinr problem, or a combination of the two, but it is a problem.

I'm working on a development site, so if there is any insight, tests, or whatever else I can offer, feel free to ping me.

jeremycaldwell’s picture

jeremycaldwell commented
Assigned: Unassigned » sociotech
sociotech’s picture

sociotech commented

Rob, Shane, Trevor,

I'm taking a look at this issue and attempting to replicate it.

Has anyone tried using the new fusion-6.x-1.0-rc1, but sticking with the older skinr-6.x-1.3?

This combination should still work, though you will lose some javascript processing for equal heights blocks and the horizontal login in-field labels.

If someone could try this and let me know if errors are still occurring then it would help to isolate the problem.

If the errors are still occurring with fusion-rc1 and skinr-1.3, then try going back to fusion-beta4 but upgrade to skinr-1.4 and see if the errors still occur.

I'll be doing the same thing to try to replicate the errors.

Thanks for your assistance!

Anonymous’s picture

Anonymous (not verified) commented

I have tried fusion-6.x-1.0-rc1 and skinr-6.x-1.3. It seems to work fine. No errors in the dblog. The Skinr functionality, which didn't show up with the newest release of Skinr, now appears.

trevorleenc’s picture

trevorleenc commented

Here's what I've got...

starting ingredients:
- fusion - 6.x-1.0-beta4
- 'slightly customized' version of acquia_prosper (css colors only, no custom code or anything like that yet)
- skinr 1.3

*Round 1*

1) upgrade base theme to fusion-6.x-1.0-rc1

result - no apparent issues

2) update to skinr-6.x-1.4

result - errors

then I went and set themes to default

after theme reset, now using garland, with fusion disabled, still getting errors

disabling skinr stopped any new errors from occuring.

*Round 2*
(same ingredients as above, but no acquia_prosper in the themes directory)

same results as above.

however, when I reset the theme back to garland, errors stopped.

*Round 3*

(before this test, I noticed when I re-uploaded the fusion theme, and went to the themes configuration page, that fusion was set as the default theme, even though it was not enabled, and before removing and re-uploading the theme, garland was set as the only enabled theme, and it was set to default. (make sense?))

1) update to skinr-6.x-1.4

same error(s) as above.

so this looks to be a skinr problem?

brentratliff’s picture

brentratliff commented

trevorleenc, good info, thanks. I am still on Skinr 1.3 with no problems as well.

gooddesignusa’s picture

gooddesignusa commented

also want to say i reverted back to skinr 1.3 and it has seemed to stop the errors.

trevorleenc’s picture

trevorleenc commented

I have also, for now, fallen back on skinr-1.3 & fusion - 6.x-1.0-beta4, along with my custom acquia_prosper based theme...and all is working.

sociotech’s picture

sociotech commented

Okay guys, thanks for the awesome feedback. I think I've got it narrowed down to the culprit, which is a patch that I recently submitted to Skinr (got in with 1.4). Working on a new patch to make it perform better (i.e., with no errors in the log). Will post for testing ASAP.

Chad_Dupuis’s picture

Chad_Dupuis commented

fwiw same problem here since upgrade to rc1 and skinr 1.4 - all was good before that. Also seeing new errors like the following (in addition to the duplicate entry item above):
call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'fusion_core_grid_block' was given in /includes/theme.inc on line 617.

The error above seems to come from random blocks and comment forms. Interestingly everything appears to work fine....

sociotech’s picture

sociotech commented

Okay, I've rolled a patch with a fix for Skinr v1.4 that should take care of the problem and make things faster as well.

I've posted the patch in a new issue in the Skinr queue in order to expedite the fix: #717644: Another system_theme_data() issue in v1.4 w/ PATCH

It'd be a big help if folks could try out the patch and make sure it works.

Thanks very much for the assistance!

espirates’s picture

espirates commented

I thought it was just me experiencing this, was about to pull the last strand of hair from my head lol

modctek’s picture

modctek commented

This problem may be related to a drupal core issue:

http://drupal.org/node/477550

I've put the patch mentioned in place, but I'm letting it marinate for a day or two before upgrading Skinr and Fusion. So far, these errors have disappeared from both of my Acquia sites.

ManyNancy’s picture

ManyNancy commented

sub

sociotech’s picture

sociotech commented
Status: Active » Fixed

New version 1.5 of Skinr released with the fix for this issue: #717644: Another system_theme_data() issue in v1.4 w/ PATCH.

Closing this issue as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.