Cannot use assign-op operators with overloaded objects nor string offsets /.../.../includes\menu.inc on line 356

i have the same error...

i guess this problem in Dhtml menu. uncheck 'display in context' in Dhtml menu settings

I get this error when trying to view an unpublished node. I can view published nodes without problems. However, if I try and publish an unpublished node, and then view it I still get the error. My nodes are published and unpublished using the nodeexpire module.

This all happened after manually running cron.php and re-indexing the site.

I don't use dhtml menu.

I fixed this by changing line 356

FROM:

  $item['type'] |= MENU_VISIBLE_IN_BREADCRUMB;

TO:

  $item['type'] = $item['type'] | MENU_VISIBLE_IN_BREADCRUMB;

I'll have a look why this happens and submit a patch if I find a good reason why PHP doesn't like the original line.

Just upgraded to Drupal 5.20 and this came back to bite me. Hmm.

After upgrading to 5.20, tried changing 356. Didn't work.

Some more clues:

This happened to me after I enabled an additional content type for one of my taxonomy vocabs then edited a node of that particular content type and saved it.

A bit of trace code revealed that the temporary "$item" array in the foreach loop in question was picking up an unstructured entry (i.e. just a string value, not an array) which caused the |= to fall over.

I.E., The output from by debug at line 337:

...
  foreach (array_reverse($location) as $item) {
    error_log(print_r($item,true));
    if (isset($_menu['path index'][$item['path']])) {
...

was (cleaned up):

Array
(
    [path] => node/529
)

Array
(
    [path] => taxonomy_menu/7/75
    [title] => Audio
)

Products

Clearing my menu cache solved the problem.

Modules that might be involved that I'm using are audio, ecommerce, taxonomy_menu, nice_menus and tac_lite.

I've not been able to reproduce it since clearing my cache_menu table but if I manage to find a reproducable instance I'll re-post.

For now maybe that will give someone a clue?

I have found the cause,
This problem occurs, if you have activated any custom module(s) for Menu.

Keep single module activated at a time.

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by fixes or patches, I am going to close this ticket. If this issue still exists and you want to continue to ask for technical support, please reopen and update this ticket.