I have setup a fresh Drupal 7 site with the following themes in sites/all/themes:

beta-7.x-2.0-beta1, gamma-7.x-2.0-beta3, omega-7.x-3.0-beta3

When I enable and set the beta theme as default, the theme is totally broken and numerous errors are rendered concerning missing variables. (see image)

This behavior also happens with the gamma theme. All other themes work fine. I wanted to try out the new fancy Omega theme system, but this has me stumped.....

The following image is of the site's home page.

CommentFileSizeAuthor
beta_error.jpg68.96 KBzoon_unit

Comments

cascadianow’s picture

cascadianow commented

Hi there, I was also having this problem. Uninstall the 7.3 version of Omega/Alpha base theme and install the 7.21 version, hopefully this will solve your problems.

zoon_unit’s picture

zoon_unit commented

Thanks for the suggestion. I wondered if that was the problem. The documentation mentions nothing about the 3.0 implementation being incompatible with prior versions. That might be an advisable change to the project page. :-) Currently, it says to install 7.x-2.1+, which would normally mean that 3.0 is also valid. (it's a higher number than 2.1)

Ideally, they will update the subthemes to be compatible with 3.0.

himerus’s picture

himerus commented

Sub themes a compatible with the same major version release (2.x, 3.x)

Updating Beta and Gamma (as well as a new theme) to 3.x is definitely on the list of todo items, but I can make no promises as to the timeline without community support as my schedule is quite packed currently, pre DrupalCon.

zoon_unit’s picture

zoon_unit commented

Would it be possible to use the Beta CSS files with a new 3.0 subtheme, or have the class names changed? I'm certainly capable of tweaking CSS for a theme, but building one from scratch is a bit above my skill level at the moment. :-)

The important thing would be to get at least ONE 3.0 subtheme available. Beta seems like a good candidate since it integrates with the color module. I am certainly willing to help with debugging and tweaking.

I would also suggest mentioning on the project pages that major release numbers are synchronized. It is not at all clear right now.

heatherann’s picture

heatherann commented

I ran into the same problem, and moved back to Omega 2.1 and it was still throwing a lot of errors. These errors went away when I enabled the Omega Starter Kit as well, in case anyone else is running into the same problem.

cpliakas’s picture

cpliakas commented

I think the big issue here is that the 2.x version is not available for download on the Omega project page, so naturally people are going to download the version that is available. Is the 2.x version of Omega un-supported?

Thanks,
Chris

aaustin’s picture

aaustin commented

Chris is right. With the 2.x version of Omega unavailable for download, this creates a very confusing situation for new Omega users - like me.

I was just looking for a head start on getting an Omega subtheme up on my site and then ran in to this issue.

Joel MMCC’s picture

Joel MMCC commented

What’s the status on this? I ran into a similar problem (no actual error messages, but no content either — just background [fortunately I’d set a different Administration theme!]).

At the very least, as #zoon_unit said in #2, the Project Page needs to be edited to warn users of this, and tell them that they must use Omega 7.x-2.1 and tell them how to acquire it, since it can no longer be obtained from the Omega page.

Or, perhaps, release a stand-alone version that includes Omega 7.x-2.1 and Beta 7.x-2.0-beta# combined, and warn users to uninstall Omega 7.x-3.x (or higher) first. This would tide us over until you can release an actual 3.x version.

adraskoy’s picture

adraskoy commented

I ran into this as well, and it's a year and a half later. The beta and gamma project pages still need to be updated. It took a bit of searching to find this.