I have Drupal 6.9 and Views 6.x-2.2 with Garland as my theme. I have changed my default color theme using the Color module. If I activate Editablefields and Ajax Load and set a field to be editable on either the node or in a View, my page will load normally with the correct colors, then as the editable field(s) load, the color scheme reverts to the default. Other pages of the site that do not display editable fields retain the correct color settings.

My apologies if I haven't provided enough or the correct info. I'll be happy to give more info on request. Thanks!

Comments

markfoodyburton’s picture

markfoodyburton commented

psychedelic :-)

Have you a different admin theme? Maybe it's getting it from there?

Cheers

Mark.

Anonymous’s picture

Anonymous (not verified) commented

No other themes enabled, sorry. I also logged in as a non-admin user to test--I get the same result.

UPDATE: I also tried the Austere theme with a color change instead of Garland. Same result--I set a different color scheme from Austere's default, and any pages with an editable field revert to its default colors.

ec’s picture

ec commented

Hi,
I can confirm this strange behavior. I also have a site with a custom Garland theme. I'm using a view with editable fields. When I go to this page view, the theme goes back to the default Garland. This behavior also occurs on node load if a field is set to editable for full node view.
Best regards,
Eric

markus_petrux’s picture

markus_petrux commented

Also happened to me. I believe this is related to ajax_load.

Anonymous’s picture

Anonymous (not verified) commented

Re #4: I couldn't find any bug reports in the ajax_load queue for this issue. markus, do you know of any other modules that depend on ajax_load? I'd like to test another module to confirm the issue is with ajax_load before I move this report.

markus_petrux’s picture

markus_petrux commented

Nope, but I tried disabling the ajax_load module, which can be done removing the dependency coded in editablefields.info, and the problem with custom colors did not happen... so I guess the ajax_load is the cause, or maybe the use of it performed by editablefields. I don't know as I haven't really investigated how ajax_load works.

markus_petrux’s picture

markus_petrux commented

I have been looking at this, and I believe my suspicions were correct, so I created a feature request for the ajax_load module explaining the situation:

#361165: Page broken when using 2 different themes

markfoodyburton’s picture

markfoodyburton commented
Status: Active » Closed (duplicate)

Sorry for my silence on this one...
This was my guess too (ajax_load)
I'll mark this as duplicate for now.

Cheers

Mark.

markus_petrux’s picture

markus_petrux commented

Hi all,

You may wish to try the mini-patch posted here:

http://drupal.org/node/361165#comment-1230518

If it works, then please post in that issue. Thanks

Anonymous’s picture

Anonymous (not verified) commented

Thanks, Mark and Markus. I've tested the patch in comment #9 and commented in the other thread.