Fatal Error: Unsupported Operand Types

What version of php are you using? (just for my graticification).

Eclipse

Can you test on 5.2.4+? 5.3 is still unsupported by much of Drupal 6 contrib, including context_admin. With the advent of the new git vcs I do hope to get the time to start fixing these sorts of issues, but I suspect this is a php version issue.

Happy I could help. 5.3 is definitely a priority for me going forward, but only really for the 7.x branch (that I'll hopefully commit today some time) so... I'm glad you like the module I have great future plans I hope to implement :-D

What part of that line is unsupported? I've come across the same issue and I'd love to help patch context_admin 6.x instead of having to roll back to a previous version of php.

caschbre: I just started looking into this but at first glance it's because module_invoke() can't be used to pass by reference.

Changing status to "active". PHP 5.3 has been out since June, 2009.

So, 7.x has fixes for this, they just need to be backported. Essentially 6.x is utilizing the plugin system incorrectly, and when we use it properly, these issues go away.

Again I'll see if I can allot some time, maybe this weekend, to backport the 7.x fixes for this stuff.

Eclipse

Eclipse,

Can you post to the patches you mentioned in case someone has time to port them.

Just some notes from investigating. Seems to be related to:

#647064: Fatal error: Unsupported operand types when menu_links query returns no results in system_admin_menu_block()

and a lot of modules are dealing with it:
#785930: Fatal error: Unsupported operand types
#595724: After core upgrade: Fatal error: Unsupported operand types ... /modules/system/system.module on line 627
....etc

For the record, I was trying to implement a page as a default local task. I switched the page to normal task and it went away. Which makes sense since that line

$item += db_fetch_array(db_query("SELECT mlid, menu_name FROM {menu_links} ml WHERE ml.router_path = '%s' AND module = 'system'", $item['path']));

is essentially asking for a normal menu item.

@jonskulski

Thanks for running that down. I'll look into it more (work's had me totally slammed lately) but I think the answer is "replace this functionality with something custom" which is actually a topic that has come up in conversation a few times. I tried to just reuse core whenever possible and that has proven to be mostly impossible, so... I guess this instance shouldn't be a surprise.

Patch attached to fix the issue, checks to see if the value returned from the module_invoke is an array() before trying to += it. Alternative approach would be to enforce that an array is always returned.