Hello

I am using Omega - Responsive HTML5 Base Theme 7.x-2.1 together with a self-created sub-theme at the moment. Since some days I am getting a message that 7.x-2.1 is not supported any more and that I should update to 7.x-3.0.

As this is only the base theme I thought updating should be easy...
But after the update all I see is a white page and lots of error messages. No layout of my website, no text nothing!
I cleared drupal’s cache. Still nothing.

Here are some of the error messages:
Notice: Trying to get property of non-object in include() (Line 37 of /home/.../sites/all/themes/subblue_7_3/templates/html.tpl.php).
Notice: Undefined variable: rdf in include() (Line 37 of /home/.../sites/all/themes/subblue_7_3/templates/html.tpl.php).
Notice: Undefined variable: doctype in include() (Line 35 of /home/.../sites/all/themes/subblue_7_3/templates/html.tpl.php).
Notice: Undefined variable: default_container_width in include() (Line 25 of /home/.../sites/all/themes/subblue_7_3/templates/page.tpl.php).
Notice: Undefined variable: default_container_width in include() (Line 15 of /home/.../sites/all/themes/subblue_7_3/templates/page.tpl.php).
(There are many more, especially about the default_container_width)

So I reinstalled Omega - Responsive HTML5 Base Theme 7.x-2.1 and everything works again.

Any idea what is happening here?

The upgrade text in the theme zip isn’t very helpful either:
“This document will provide an outline of upgrading Omega 2.x subthemes to Omega 3.x
@todo”

Will this happen every time you bring out a new version of Omega? I thought this is a stable framework and I would only need to update the base theme from time to time and my subtheme would still work...

Comments

himerus’s picture

himerus CreditAttribution: himerus commented

Updating between MAJOR releases (2.x > 3.x) is not just drag & drop... the structure of the theme is changed.

Yes, support issues for the 2.x version is no longer supported. Upgrading to 3.x is recommended when possible, but will take template and CSS changes.
If you have a site running 2.x and have no real need to update to the new features in 3.x, you can happily stay on the 2.x version, but 3.x is recommended for ALL new sites using Omega.

At some point, I do hope that I (or someone in the community) can accurately document the upgrade process on subthemes in Omega 2.x to 3.x.

federico.bebber’s picture

federico.bebber CreditAttribution: federico.bebber commented

2.x > 3.x is a major version upgrade, so it's quite easy that things get broken
anyway i read that there will be some hints soon on how to upgrade from 2.x to 3.x
personally i just uninstalled omega-delta-omega_tools, installed new versions, added my custom css and recreate the delta templates cause it was a simple website. (remember to run update.php)
my 2 cents

MJH’s picture

MJH CreditAttribution: MJH commented

|himerus:
|"If you have a site running 2.x and have no real need to update to the new features in 3.x, you can happily |stay on the 2.x version, but 3.x is recommended for ALL new sites using Omega."

The only "problem" with still using V2.x is the big warning message in the admin-section of my website that I should update to V3.x immediately.

And in the status report:
"The installed version of at least one of your modules or themes is no longer supported. Upgrading or disabling is strongly recommended. See the project homepage for more details. See the available updates page for more information and to install your missing updates."

That's a bit annoying...

MJH’s picture

MJH CreditAttribution: MJH commented
Issue summary: View changes

-

Argus’s picture

Argus CreditAttribution: Argus commented
Status: Active » Closed (works as designed)

Annoying it might be, it's the price we pay for the big changes. The warnings come from core modules and functionality, as far as I'm aware of there is nothing that can be done to prevent them. Of course they can be turned of.... ;)

Closing the issue.

teamA’s picture

teamA CreditAttribution: teamA commented
Priority: Normal » Major
Status: Closed (works as designed) » Active

Hi,

I was using the 2.x version of Omega, and as my site is still in development we wanted to step up to 3 so that future updates when the site is live will be less scary.

I first tried to use the Omega Tools subtheme creator - this resulted in a WSOD. I went and checked the created directory - all of folders were there, but were empty! I then went ahead and created a new .info file from the started kit and transferred over all of the necessary files. Now I get the following errors:

Notice: Undefined variable: default_container_width in include() (line 15 of /home/drycool2/xxx.com/sites/all/themes/xxx/templates/page.tpl.php).
Notice: Undefined variable: default_container_width in include() (line 16 of /home/drycool2/xxx.com/sites/all/themes/xxx/templates/page.tpl.php).
Notice: Undefined variable: default_container_width in include() (line 24 of /home/drycool2/xxx.com/sites/all/themes/xxx/templates/page.tpl.php).
Notice: Undefined variable: default_container_width in include() (line 25 of /home/drycool2/xxx.com/sites/all/themes/xxx/templates/page.tpl.php).

My page.tpl.php is calling in zones correctly. What other steps do I need to take here?

All themes are at sites/all/themes/ So that means I have
sites/all/themes/omega
sites/all/themes/xxx

Please help, my site is hosed and a task I though would take an hour or less is holding up the entire team.

Thanks,
Aris

teamA’s picture

teamA CreditAttribution: teamA commented
Status: Active » Closed (fixed)

OK, I remade the subtheme again, manually and this time it worked. Not sure why.

Can you clear up one question - should the Alpha theme be enabled, or not?