color.module resets main domains theme

I stepped into the same problem few days ago. Simply re-saving the main site theme configuration (that is: admin/build/themes/settings) fixed it for me, in Garland.

I don't know that it is fixable. This keeps coming up over and over again.

It's a problem with how color module stores data.

The 6.x branch is essentially critical bugfix only, so I don't intend to even look at this issue unless there is a patch.

BTW: I think this only happens if the main domain isn't set (is using 'default'). So the fix may be to simply save settings for the primary domain first.

*crashes* is the wrong term here.

Steps to replicate.

-- Set the primary domain theme.
-- Set a secondary domain theme to 'default'. It will inherit settings from the primary domain.
-- Set the secondary domain theme to something other than default. It will remove the settings for the primary domain.

If you can figure out how to stop this behavior, go for it, but color.module is a nightmare.

You might be able to trick this by removing the 'Bluemarine (default)' option on domain-specific settings forms. Just replace it with parameters that are 1 off. (e.g. #dc1234 becomes #dc1233). That should fool color.module.

Well, it does fool color.module, but then it thinks you have saved a custom theme.