When updating one of my projects from 7.x-4.3 to 7.x-4.4, I got a fatal error when running the DB updates.

This is what was shown in the browser:
Fatal error: require_once(): Failed opening required '/Users/[user]/Sites/[site folder]/sites/all/themes/omega/omega/panels/layouts/omega/omega.inc' (include_path='.:/Applications/DevDesktop/common/pear:/usr/lib/php') in /Users/[user]/Sites/[site folder]/sites/all/modules/ctools/includes/plugins.inc on line 475

All other modules are updated, and working fine.

Apparently a conflict with cTools. I'll see if there's time later to root it out. For now, I rolled back to 7.x-4.3 and pulled in the backed-up DB.

Comments

karolus created an issue. See original summary.

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Fixed

Did you use the Update Manager UI to download the new version? If so, don't. The module/theme download feature of Update Manager is a fundamentally broken concept (for various other reasons). Due to the directory structure of Omega, it also fails to properly place and extract any new version of the theme. So please use drush or manually download it instead! Please re-open if that's not the case.

sashken2’s picture

sashken2 CreditAttribution: sashken2 commented

I have same problem too

fubhy’s picture

fubhy CreditAttribution: fubhy commented

Did you read my answer?

karolus’s picture

karolus CreditAttribution: karolus as a volunteer commented

Thanks--
That was indeed the way I updated. Once my deadline projects wrap up, I'll go ahead and verify this.

zeldesign’s picture

zeldesign CreditAttribution: zeldesign commented

Thanks, Fubhy for the advice.
I followed it and still got the same issue?
I downloaded 4.4 version and uploaded it into [sites]->[themes] folder, replacing my previous (4.3) version. Next to it is my my omega [subtheme] folder and also [at_panels_everywhere] folder. Is that the right architecture? Maybe I need to upload it one level deeper, next to [ohm] folder? Do I need to do something with my subtheme?

zeldesign’s picture

zeldesign CreditAttribution: zeldesign as a volunteer commented

Just to confirm - I uploaded it one level deeper and voila! - it worked like a charm.
So delete contents of your old Omega Folder, but keep the folder itself and bury the FOLDER of the 4.4 version there. Hope this will help someone. :)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

karolus’s picture

karolus CreditAttribution: karolus as a volunteer commented
Status: Closed (fixed) » Needs work

OK--
I did a manual update via zeldesign's suggestion in #7. It took a bit of fiddling, since there are a number of levels within the base theme that look identical. Would there be a way to make this easer?

P.S.--I did try via drush first, and the message given was that "Project has no enabled extensions and can't be updated", and listed the installed version as 7.x-4.2, even though the version listed in the GUI of my installation (admin/reports/updates) was 7.x-4.3.

steinmb’s picture

steinmb CreditAttribution: steinmb as a volunteer commented
Category: Bug report » Support request
Priority: Major » Normal
Status: Needs work » Fixed

Project has no enabled extensions and can't be updated - Just mean the theme/module is not enabled. Either that is true or you are running drush against the wrong installation.

Normally when you manually do a upgrade you remove the entire directory containing the module/theme and replace it with the new version. Do not try to puzzle a old and new version together. That just leads to pain and suffering. I'll assume your modifications/theme lives in a separate subtheme outside Omega.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.