I tried updating two of my sites to Omega 8.x-5.0-alpha6. Both crashed. All I got was a white screen. Both have extensive CSS in a child theme. They are based on the starter theme which doesn't seem to have gotten an update. Do you I need to create the child themes again?

I got the sites to start again by putting back the older version of Omega.

Suggestion on how to update without it crashing?

Comments

leeoh created an issue. See original summary.

leoraw’s picture

leoraw CreditAttribution: leoraw commented
Title: Site with child theme crashes after 8.x-5.0-alpha6 update » Site with child theme crashes after Omega 8.x-5.0-alpha6 update
Issue summary: View changes
himerus’s picture

himerus CreditAttribution: himerus as a volunteer commented

These should help:

#2767217: Rename style-vars.scss to _style-vars.scss
#2767061: Rename layouts.yml to avoid potential conflicts with layout_plugin

You will need to make these edits, and assuming ALL configuration updates have been exported properly or backed up, uninstall and reinstall your child theme.

leoraw’s picture

leoraw CreditAttribution: leoraw commented

Thanks - I will give this a try tomorrow. Just those two renaming of files? (I was originally thinking I would just rebuild the child theme, but I wouldn't want to do this each time there is in update to the main theme).

Hm ... is there a way to easily export the configuration of the theme? I will look into that as well.

leoraw’s picture

leoraw CreditAttribution: leoraw commented

I ended up rewriting the whole child theme. I think part of the problem was I had written the child theme wrong - I had included the starter kit directory. One of my test sites updated fine - but my other site did not. I haven't tried the main site at all.

I'm trying to figure out how to get this to work. It doesn't run the main Omega theme at all - that one also crashes. I now have it in Bartik.

leoraw’s picture

leoraw CreditAttribution: leoraw commented

This is the error that I am getting:
Template "themes/omega/omega/omega/templates/html.html.twig" is not defined (Drupal\Core\Template\Loader\ThemeRegistryLoader: Unable to find template "themes/omega/omega/omega/templates/html.html.twig" in the Drupal theme registry.).

leoraw’s picture

leoraw CreditAttribution: leoraw commented

I tried to install Omega 8.x-5.0-alpha7 on my test site. I uninstalled all the other themes. It crashes when I just load Omega alone. I now have it running in Bartik. If I had another good theme, I would switch. Not enough themes to choose from yet. Hope you can help me with more details on how to proceed.

leoraw’s picture

leoraw CreditAttribution: leoraw commented

Good news ... I tried Omega 8.x-5.0-alpha7 on a local copy of the exact "real" site, and the update worked! I assume as this is still alpha, it has more changes ahead. Should I plan on rebuilding my child theme (preferably automated, through a dashboard, so I don't get anything wrong) at some point? I notice the one I have now says alpha6. I didn't change the names of any files when I did this update.

leoraw’s picture

leoraw CreditAttribution: leoraw commented

Sadly, I tried the Omega 8.x-5.0-alpha7 update on the Pantheon site (after success on my local set up), and the theme update crashed the site. I restored from backup. Sigh.

himerus’s picture

himerus CreditAttribution: himerus as a volunteer commented
Title: Site with child theme crashes after Omega 8.x-5.0-alpha6 update » Site with child theme crashes after Omega 8.x-5.0-alpha7 update
Version: 8.x-5.0-alpha6 » 8.x-5.0-alpha7

Sadly, this IS the nature of theme upgrades in general. Still in Drupal 8, themes are not modules, and thus don't have an ability to run update hooks.

At ANY point on ANY theme, at ANY release level (alpha, beta, stable) changes can be applied to the base theme that would require you to make updates to your own theme/templates as well.

Assume an update comes in that requires new markup in html.html.twig and adds in a few more tags. If you have a copy of that file in your theme that you were making customizations to, then the update to the template in a future Omega release would leave you without the update. You'd HAVE to manually apply the markup changes for them to appear in your theme.

Now, since this 8.x-5.x branch is still in alpha, and under some fast and loose implementation of fixes and features, there ARE going to be multiple situations where changes are made that WILL DEFINITELY require updates to any subthemes created. I'll do my best to 'document' this, but sometimes it's a bit difficult.

If you look at the comment on the release node for the latest alpha: https://www.drupal.org/project/omega/releases/8.x-5.0-alpha7 You'll see the _style-vars.scss needs to be renamed to _omega-style-vars.scss and any references in any scss files you may have would also need to be updated. That (at the time of release) I think was the only big issue between alpha6 > alpha7. If your previous version was older, then well, there were many additional changes.

The only way to be 100% sure of what might have changed that may affect your child theme is to follow the commit history, look for file renaming, variable renaming, etc.

Finally...

Once Omega Five reaches a Beta release, in theory there should be no 'breakages' of subthemes that are created. That will mean installing the new version shouldn't break things, or much more detailed changelog records will be kept with details on upgrades between versions.

Your situation is normal. It's not just you. Theme upgrades are a challenge all on their own with absolutely no comparison to module upgrades.