On node/add/blog:

Fatal error: Call to undefined function custom_breadcrumbs_simple_breadcrumb_table() in /var/www/sites/all/modules/custom_breadcrumbs/custom_breadcrumbs.module on line 163

I'm running the dev from May 30.

CommentFileSizeAuthor
#4 480774-4.patch1.67 KBroderik
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

domesticat’s picture

Priority: Critical » Minor
Status: Active » Fixed

Heh, okay, I'm marking as 'fixed' since I just verified the mistake was mine. Here's the process that got me to this point, so you can decide if you want to tweak the documentation, and to save someone else from a moment of panic.

  1. I was running the old version of custom_breadcrumbs. Tried to write a new taxonomy-based breadcrumb using PHP, and it didn't work -- duh!
  2. I saw that taxonomy breadcrumbs were included in the new dev version. Ran update.php, checked the pages for which I'd written the taxonomy-based breadcrumb, and saw all the breadcrumbs were working properly.
  3. Since all seemed well, I never thought to check admin/build/modules to see if there were extra parts to enable.
  4. Next morning, when I tried to post a new node, I got the PHP error. Enabling the correct submodule fixed the problem immediately.
MGN’s picture

Glad to hear it worked out. I was thinking I may have missed a require_once for custom_breadcrumbs.admin.inc. I'll look into that just to be sure. Enabling the submodule probably triggered the load of the include file.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

roderik’s picture

Status: Closed (fixed) » Needs review
FileSize
1.67 KB

It's back.

MGN’s picture

Status: Needs review » Reviewed & tested by the community

Thanks. This is fixing an error that came in with rearrangements introduced in #1089844: Make taxonomy-based breadcrumbs for nodes predictable?.

MGN’s picture

Status: Reviewed & tested by the community » Fixed

Modified patch slightly to use module_load_include instead of require_once. Committed to 6.x-2.x-dev.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.