By axon on
Can anyone help me, I got this notice:
Undefined index: highlighted in include() (line 120 of /home/xxx/public_html/modules/system/page.tpl.php).
what can I do about it?
Can anyone help me, I got this notice:
Undefined index: highlighted in include() (line 120 of /home/xxx/public_html/modules/system/page.tpl.php).
what can I do about it?
Comments
You need to define a region
You need to define a region called highlighted in the .info file from your theme.
Drupal 7.10
I'm getting the same message but with addition:
Who do I address these too?
Are these being fixed so I
Are these being fixed so I can upgrade?
Cancel that! I found the
Cancel that! I found the problem! I didn't move my site over.
what was it?
I'm having the exact errors involving migrating a site, how did you fix yours?
Suggestion
I ran into this cascading semi-failure with confusing stacks of errors being reported in the course of development for 'beyond-features/strongarm' deployment versioning and synchronization. I was able to track the error to some site values in the variables table that hadn't been properly serialized, so a few strings got inserted directly. When Drupal tries to unserialize these, some of these base-level site vars are not set properly and 'kablooey' (I believe that's the correct technical terminology).
The error that was illustrated here would seem to hint that the 'Theme default' value is not set properly. Two things to validate in the variables table in this occasion are:
"SELECT * FROM variable WHERE value = '' OR value IS NULL;"Note: even NULL value should be serialized as a boolean value (I believe)
If inserting/updating values into the variables table via direct SQL, as opposed to using the variable_set() function, be sure to properly encode each of the values being inserted, updated, or replaced in the SQL.
Disclaimer: I am not recommending that the variables table be updated directly if at all possible, this can lead to serious config issues. My scenario had to do with 'priming the pump' with some low-level site config values that seemed to be inaccessible via Strongarm due to the bootstrap processing order hierarchy, that is unless called from the low-level hook 'hook_stream_wrappers()'. There is a full discussion on the this in the Strongarm issue queue: strongarm_set_conf() needs to be called sooner
My solution was to parse an array of the 'variable' table's name values that I needed from the system.admin.inc file, using the following function, and then pull their values using variable_get(), or SQL select statement, into an associative name=>value array by iterating through the name values array. If using the varible_get() method, the variable values can be re-serialized and SQL-safe encoded using the above '_set_sql_safe_string()' function with serialize:
$sqlval = _set_sql_safe_string( serialize($val) ).Hope this makes sense and is helpful!