I upgraded to 3.0-rc2 from 3.0-beta2 last week to fix another strange bug (see http://drupal.org/node/1232594) with incorrect ordering of blocks on the front page.

A manual upgrade (swapping out the old /sites/all/themes/omega folder for a new omega folder) causes bizarre results, particularly in how the page's HTML is assembled. All pages were missing the H1 header and the tabs with a few exceptions: if the page had a view with tables in it, the page would be unaffected by this bug. Also, the main column would start wrapping around the left navigation. Further examination of the rendered HTML code showed that several major HTML components were missing. (see the attached image)

We tried clearing the caches, switching off the responsive grid, and every nonessential stylesheet and setting, but that didn't fix the issue. I tried reverting the code from rc2 back to beta2 and the issue persisted. We rolled back core from Drupal 7.7 to 7.4, as well as a few module updates, thinking that the issue might be related to the interaction of these with omega 3.0.

In the end, we had to restore the site to the last set of nightly backups and a tarball of the entire made a few days earlier. Our site went live with the wrong order of blocks on the front page.

The site is now live with 3.0-beta2. I've made a second attempt to upgrade the the site to 3.0-rc3 and the issue persists. We can keep a dev version of the site up temporarily at http://sesync.traktekpartners.com if it helps diagnose this bug.

CommentFileSizeAuthor
omega-issue-screenshot.jpg175.33 KBmodulist
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

fubhy’s picture

Priority: Critical » Normal

I saw that you updated to RC3... Did that fix it?

thomasLausZ’s picture

maybe the Omega "Toggle styles" overrides some of you css?

modulist’s picture

No, @fubhy, the update to RC3 actually duplicated the same problems as upgrading to RC2

modulist’s picture

@thomasvum: We have tried using "Toggle styles" on the site with all style sheets on and all off, save styles.css. The problem is not one of CSS overrides, but instead of the HTML for the page not being assembled properly. The H1 elements and the tabs simply do not appear anywhere in the source code on the affected pages.

fubhy’s picture

Did you maybe deactivate them in your theme settings? "Toggle elements" / "Toggle advanced elements" ?!

fubhy’s picture

It would probably be best if you can send me the URL + Login to a development copy of that website + theme so I can check it myself. Is that possible?

modulist’s picture

@fubhy I'll be happy to send you credentials to the development server. I can definitely rule out "toggle styles" as a source of the problem, as the site's also missing Drupal interface elements, such as tabs and contextual links (http://sesync.studiomodule.com/about-us)

I upgraded to the full 3.0 release, and this bizarre behavior continues. What's even more baffling is that the problem with the missing HTML and page elements persisted, even when I switched off my child theme and made Omega the default.

I'm inclined to believe that the problem may stem from the issues I had installing Omega in the first place. Omega gave me quite a bit of trouble with drush and auto-install on a CentOS server that was running PHP 5.2. While I have upgraded to PHP 5.3 since, I do wonder if the original installation may have been flawed. I'm tempted to wipe out Omega to reinstall it and start over to see if the problem persists.

If that's the case, then PHP 5.3 should be an installation requirement for installing Omega, and the installer should check for that dependency.

apmsooner’s picture

I initially had similar problems when doing the automatic update through the drupal ui but later, i tried again the old manual way by disabling omega and setting default theme to bartlet. Then just replaced the omega folder and reenabled my subtheme and all is fine. The only thing i can say is that the automatic update caused me major issues....

brunodbo’s picture

Title: Missing HTML in content region » Upgrades to 3.0-rc2 and 3.0-rc3 cause missing HTML, other bizarre behavior
Version: 7.x-3.0 » 7.x-3.0-rc3

I created a subtheme using Drush yesterday using Omega v7.x-3.0, and having the same problem: page title and local tasks are missing in the page's html. They're toggled 'on' (checked) in the theme's config.

brunodbo’s picture

For some reason, path_to_theme/omega/omega/templates/region--content.tpl.php (containing $title, $tabs, ...) is not being used. The default path_to_theme/omega/omega/templates/region.tpl.php is used instead.

brunodbo’s picture

I came back to this one today, and found the reason why the default region.tpl.php is used instead of region--content.tpl.php (which contains the HTML that seems to be missing).

I installed my site using my own installation profile that I'm building for a site, which didn't put any content (ie. blocks) in the content region yet. As stated on http://drupal.org/node/1089656:

The region template is used when a page region has content, either from the Block system or a function like hook_page_build().

Putting the 'Main page content' block in the 'Content' region fixes this issue for me: when the region has content, omega's region--content.tpl.php is picked up, and works as expected.

brunodbo’s picture

Version: 7.x-3.0-rc3 » 7.x-3.0
brunodbo’s picture

Title: Upgrades to 3.0-rc2 and 3.0-rc3 cause missing HTML, other bizarre behavior » Missing HTML in content region

Clarifying title.

PCateNumbersUSA’s picture

I'm having the exact same problem. "Main page content" is already in the content region. I did a manual sub theme install. Anyone know of any other possible fixes?

Cellar Door’s picture

Title: Upgrades to 3.0-rc2 and 3.0-rc3 cause missing HTML, other bizarre behavior » Missing HTML in content region
Version: 7.x-3.0-rc3 » 7.x-3.0

PCateNumbersUSA - Can you clarify what the issue you're seeing is? The above issue was due to a custom install profile, did you use a custom install profile as well? Have you tried using drush or the UI wizard provided by omega-tools to create the subtheme? There could be something missing from your manual subtheme creation that is causing this as well.

Also, if you hop into the IRC room #drupal-omega there's a bunch of us in there that can walk you through this quickly as this isn't a common issue on omega installs.

lefnire’s picture

Same thing. Fresh install with OpenOutreach (install profile), Omega-7.x-3.1, added "Main Page Content" block into "Content" region -- no cigar. This happens when using Omega default theme too, not just subtheme, and after resetting the theme and making sure the nothing's disabled. Elements are simply not available to the HTML (not hidden with CSS).

cgdrupalkwk’s picture

I had the same problem, none of the "Content" HTML was present. I was using Delta and Context to setup custom region and block layouts for different sections of the site. I removed all blocks from Drupal Block module and was managing all of them thru the Context module. This error occurred when the "Main Page Content" was not placed in the "Content" region and immediately resolved itself after adding the "Main Content "Page" block to the "Content" region under Drupal's block module while still using Context to manage all other blocks keeping the "Main Page Content" block on the sideline in all Context setups.

Cellar Door’s picture

Status: Active » Closed (works as designed)

When using Context to place blocks you still need to keep main page content placed in the content region in order to keep things in line. I don't think this is exclusive to Omega but more of a core issue for D7.

If you want to use context exclusively make sure the main page content is placed via the system blocks and the rest can be handled via context.

mngates’s picture

Thank you for your help!

http://drupal.org/node/1239944#comment-5248352 (#11) is the best comment I have seen on this item, at least for my case. I was banging up against walls trying to find why the region--content.tpl.php was not showing the tabs. There was no "Main Content" block, so I added a new block and put in a small "Powered by Drupal". With global.css, added a display:none to it. Works great!

Just posting in case anyone else wants to do something similar.