After upgrading to the new theme version -- by manually replacing the old omega superfolder with the new omega superfolder -- I get this error on all my pages:

Fatal error: [] operator not supported for strings in [redacted site path]/sites/all/themes/omega/alpha/template.php on line 76

I would appreciate any assistance.

Thanks!

Comments

spacegoat1701’s picture

spacegoat1701 commented
Status: Active » Fixed

Upgrading to the latest .dev version appears to have fixed the issue.

Ankabout’s picture

Ankabout commented

Same problem here, but for the latest dev as well.

Fatal error: [] operator not supported for strings in /my/site/sites/all/themes/omega/omega/template.php on line 147

fubhy’s picture

fubhy commented

Please guys! Don't overwrite your existing omega folder with the new one... DELETE the existing omega folder and then PLACE the new omega folder where the old one was.

Argus’s picture

Argus commented

Perhaps your comment here has set people on the wrong track: "Clear your Cache after overwriting your current Omega installation!" :)

Ankabout’s picture

Ankabout commented

Just a note. In the beta1 version, there is an error on line 51 of \omega\preprocess\preprocess-node.inc.

I copied that line, and placed it in my own preprocess function, this was causing the error. This is the code concerned (last line):

  // Add a class to make the node container self clearing.
  $vars['attributes_array']['class'][] = 'clearfix';
  
  $vars['content_attributes_array']['class'] = array('content', 'clearfix');
  
  // Adding a class to the title attributes
  $vars['title_attributes_array']['class'] = 'node-title';

Fixed now for me, with rc1.

Status: Fixed » Closed (fixed)

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

michaelfillier’s picture

michaelfillier commented

I received the same error while trying to test out the new inline editing initiative of spark. After disabling edit and fape, everything went back to normal. I was using omega 7.x-3.1.

The edit project is aware of the bug, a fix is in the works, looks like the issue was resolved: http://drupal.org/node/1672248.