upgrading from pre-rc3 versions for sites using custom libraries requires resaving the theme form

[labboy0276]

When upgrading to 3.0 on a rc2 or rc3 branch I am noticing that the custom lib is not being seen. The work around is going in and re-saving the subtheme and it alleviates the issue.

[pirog]

Good to know. Do you know why this happens?

[labboy0276]

i am investigating

[pirog]

solid!

On Wed, Jul 2, 2014 at 9:14 AM, John Ouellet notifications@github.com
wrote:

i am investigating

—
Reply to this email directly or view it on GitHub
#105 (comment)
.

Cheers,

Mike Pirog
Kalamuna
www.kalamuna.com

[labboy0276]

I poked around many places, I looked for possibly subtheme_bootstrap not being set properly, but it all seems ok. Somehow, somewhere it is not seeing the custom bootstrap library on update.

Any other places to look would be helpful, but since the code base is so different, something isnt happy on upgrade.

[pirog]

Does clearing the cache also resolve the issue in lieu of saving the form again?

[pirog]

and are you sure it breaks from rc3 or just from rc2?

[labboy0276]

rc2 only

rc2 -> 3.0 = no bueno. So maybe just recommend a step upgrade then, or resave the subtheme if you dont?

[pirog]

well im guessing an upgrade from rc2->rc3 also breaks so i dont think a step upgrade would do much of anything.

we need to have some sort of mechanism to map rc2 settings to rc3+ settings. i dont think update hooks are viable for themes but other themes MUST change their settings from version to version so we should see what they do and whether that would make sense here.

[labboy0276]

yes, this is true.

I will stare at some other themes and see