Upon core upgrade to 7.22, I'm now getting the following error:

Notice: Undefined index: process functions in aurora_theme_registry_alter() (line 68 of .../sites/all/themes/aurora/template.php).
Warning: array_search() expects parameter 2 to be array, null given in aurora_theme_registry_alter() (line 68 of .../sites/all/themes/aurora/template.php).
Warning: array_splice() expects parameter 1 to be array, null given in aurora_theme_registry_alter() (line 69 of .../sites/all/themes/aurora/template.php).

Lines 68 and 69 of aurora/template.php read:

 if (($index = array_search('template_process_html', $registry['html']['process functions'], TRUE)) !== FALSE) {
    array_splice($registry['html']['process functions'], $index, 1, 'aurora_template_process_html_override');

Has anyone else run into this? Any idea what I need to fix?

Comments

skt’s picture

skt commented
Priority: Normal » Major

Still seeing this issue. I've tried uninstalling & reinstalling aurora, but no change.

Snugug’s picture

Snugug commented
Status: Active » Closed (won't fix)

This functionality has been moved to Magic and is no longer part of Aurora. Please upgrade to Aurora 3.x and Magic, and if this issue persists, report it in the Magic issue queue.

skt’s picture

skt commented

Thanks, Sam. I went ahead and did as you suggested - I upgraded to Aurora 3.x, installed Magic and the other modules listed in the new docs. No more "undefined index warning" so that's good.

BUT.... I then went and created a new aurora subtheme using susy. I copied over the Gemfile from the base theme. Made some changes to the Sass files. On running "bundle exec compass watch" I get:

LoadError on line 161 of /Library/Ruby/Gems/1.8/gems/compass-0.12.2/lib/compass/configuration/data.rb: no such file to load -- aurora

Tried updating compass-aurora, but that didn't help.

I'm still able to run "bundle exec compass watch" on the old subtheme.

I'm not well-versed with Ruby gems, so I'm at a loss as to what this error means or how to fix it. Any help would be greatly appreciated.

Snugug’s picture

Snugug commented

Please file new tickets for unrelated issues

skt’s picture

skt commented

Of course, sorry about that. It's here: http://drupal.org/node/1993960

skt’s picture

skt commented

Just a follow-up comment... if it's still ok to run Aurora 2.7 (using Bundler to manage dependencies), shouldn't the "Undefined index..." notice be possible to resolve without upgrading to Aurora 3? I'm using the example Gemfile for 2.7 on the project homepage. Would I need to add something to it? Or, are there modules incompatible with Aurora 2.7 that would cause the warning?

Snugug’s picture

Snugug commented

There are two different things at play here: the PHP base theme and the sub theme. Bundler only manages the dependencies of your Ruby gems that are needed for Compass extensions when writing your CSS, not the PHP base theme. While I see no issue with upgrading to Aurora 3.x PHP code while still using pre-Aurora 3.x subthemes, there are some upgrade steps you're going to need to take to ensure all of your settings migrate properly to Magic.

skt’s picture

skt commented

Thanks.... I guess what I'm trying to understand is what I'd need to do to continue using 2.7 & not get the Undefined index error. You mention that certain functionalities have been moved to Magic for the Aurora 3 release; but if I'm still using 2.7 + Bundler + Gemfile as specifed in docs, shouldn't that work as well?