Error on node edit when using "Custom breadcrumbs for paths"

I've tried, but haven't been able to reproduce this.

This issue occurs on node edit as well. The error appears in the core admin theme with the overlay. This also caused issues when deleting files from affected nodes. I use the "Use wildcard pattern matching in paths " setting which may be causing the issue.

I was able to resolve the issue with deleting files by excluding the module on node/*/edit pages; however, the error still occurs:

    Warning: Illegal offset type in isset or empty in drupal_lookup_path() (line 125 of /home/user/public_html/dev/includes/path.inc).
    Warning: strtok() expects parameter 1 to be string, array given in drupal_lookup_path() (line 131 of /home/user/public_html/dev/includes/path.inc).
    Warning: mb_strtolower() expects parameter 1 to be string, array given in drupal_strtolower() (line 476 of /home/user/public_html/dev/includes/unicode.inc).
    Warning: Illegal offset type in isset or empty in drupal_lookup_path() (line 125 of /home/user/public_html/dev/includes/path.inc).
    Warning: strtok() expects parameter 1 to be string, array given in drupal_lookup_path() (line 131 of /home/user/public_html/dev/includes/path.inc).
    Warning: mb_strtolower() expects parameter 1 to be string, array given in drupal_strtolower() (line 476 of /home/user/public_html/dev/includes/unicode.inc).
    Warning: Illegal offset type in isset or empty in drupal_lookup_path() (line 125 of /home/user/public_html/dev/includes/path.inc).
    Warning: strtok() expects parameter 1 to be string, array given in drupal_lookup_path() (line 131 of /home/user/public_html/dev/includes/path.inc).
    Warning: mb_strtolower() expects parameter 1 to be string, array given in drupal_strtolower() (line 476 of /home/user/public_html/dev/includes/unicode.inc).

Error Message On Node Edit Pages triggered by problem in d7 version of custom breadcrumbs.

Ideally if that bug is fixed all that needs to be done is at @ admin/config/user-interface/custom-breadcrumbs Check the Advanced Settings "Use wildcard pattern matching in paths" and on Excluded Paths add node/*/edit .

Bug is:
This setting for excluded paths is currently not being respected by the custom_breadcrumbs module hence the error.

The problem is still present in Drupal Core 7.9.

I have traced this back to custom_breadcrumbs_paths_cb_node_form_table from (via custom_breadcrumbs_form_node_form_alter and _custom_breadcrumbs_match_path).

This function seem to be getting a node where the path has been set to an Array (not a string).

[path] => Array
(
[pid] => 192
[source] => node/99
[alias] => news-media/sa-p-p-s-h-m
[language] => und
[pathauto] =>
)

Possibly related: #1266502: Illegal offset type in isset or empty in path.module

This little fix works for me...

Changes to the above patch:

• Added a comment & whitespace around stanza.
• Removed dependency on operator precedence rules.
• Added Git metadata.

Confirming patch in #10 gets rid of errors.

Patch on #10 works for me too. Thanks!

Hopefully it's the right solution. :)

Patch works.

As w.m. mentioned above, the problem occurs when $node->path is set to array('pathauto' => TRUE).

custom_breadcrumbs_paths_cb_node_form_table() sends this array to drupal_lookup_path() which actually requires a string.

Edit: Found a bug with the patch. See next post.

The patch doesn't account for array('pathauto' => FALSE) (i.e. when pathauto is enabled but not generating a new alias). The condition should be isset($node->path['pathauto']) rather than $node->path['pathauto'].

I've attached a new patch.

Righto, works. All I did was add Git metadata.

applied patch
excluding the module on node/*/edit pages
cleared cache

no more errors

same error, Drupal 7.14 if "Use wildcard pattern matching in paths" is enabled.

- applied patch
- excluding the module on node/*/edit pages -> wildcard seems not work if the wildcard is not on the end of the string.

But: if I change the module weights, errors are gone.

Module weight with "Illegal offset type in isset or empty" Errors:
Custom breadcrumbs for taxonomy
Custom breadcrumbs for paths
Custom breadcrumbs for views
Custom breadcrumbs

Module weight without "Illegal offset type in isset or empty" Errors:
Custom breadcrumbs
Custom breadcrumbs for views
Custom breadcrumbs for paths
Custom breadcrumbs for taxonomy

This is actually the proper fix. $node->path is *not* a string in Drupal 7 and this function *should not* be modifying the node object either.

Thank you all for the patch!
Every time I go to any node edit page, I was getting the same three errors six times over.

Message	Warning: mb_strtolower() expects parameter 1 to be string, array given in drupal_strtolower() (line 476 of /var/www/vhosts/tlthost.net/httpdocs/includes/unicode.inc).

Message	Notice: Array to string conversion in drupal_lookup_path() (line 131 of /var/www/vhosts/tlthost.net/httpdocs/includes/path.inc).

Message	Warning: Illegal offset type in isset or empty in drupal_lookup_path() (line 125 of /var/www/vhosts/tlthost.net/httpdocs/includes/path.inc).

I finally narrowed it down to the "Use wildcard pattern matching in paths" setting. The #19 patch fixed it so I could keep using wildcards in my breadcrumbs.

i can confirm that #19 indeed gets rid of the errors; however wildcard paths do not work.

i have a simple path of node/*/edit with simply:

title = junk
path = node

and bcrumb on a node edit page is unaffected.

thought i would debug this a bit and see what's going on; turns out theme related.

i am using Omega and it breaks the cb module trying to set the bcrumb for the edit page - i could see that the path was being matched and the trail getting passed to drupal_set_breadcrumb() is correct; but it was being unaffected. Changing to Bartik and the crumb works as defined with CB.

oddly though, the actual node page which has it's trail defined by a Node setting in CB; this works ok even in Omega. I'll check Omega queue and see if i can find why Omega is forcing bcrumbs on edit pages.

Patch on #19 works for me

#19 works for me too. thanks!

#19 works for me too and also fixes a related problem where the Workflow module's form was not saving values on the node edit page.

Committed #19 in 51e18d0.

@liquidcms: Sounds like a separate issue?