Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Just update custom_breadcrumbs to 6.x-1.5, and get the following fatal error:
Fatal error: Call to undefined function custom_breadcrumbs_load_breadcrumbs() in sites/all/modules/custom_breadcrumbs/custom_breadcrumbs_paths/custom_breadcrumbs_paths.module on line 141
Comments
Comment #1
MGN CreditAttribution: MGN commentedYou must have upgraded to 6.x-2.x, since custom_breadcrumbs_paths.module isn't part of the 6.x-1.x version. Can you double-check your current version and let me know what version you upgraded from?
Did you run update.php when you upgraded?
Can you explain when in the upgrade process you saw the error?
This may be related to #530638: Fatal error when running update.php.
Thanks
Comment #2
MGN CreditAttribution: MGN commentedclosing since its been a long time without followup.
Comment #3
Brian294 CreditAttribution: Brian294 commentedI was able to reproduce this issue. I used drush dl custom_breadcrumbs to upgrade from 2.0 beta2 to 2.0 beta3. Drush, for some reason, ran out and downloaded 1.5 overtop of my existing 2.0 installation and gave me the following error:
Fatal error: Call to undefined function custom_breadcrumbs_load_breadcrumbs() in/home/.../public_html/sites/all/modules/custom_breadcrumbs/custom_breadcrumbs_paths/custom_breadcrumbs_paths.module on line 166
I believe drush uses the recommended version (1.5), not necessarily the next highest version within the version branch (2.0-beta3).
Peace,
Brian
Comment #4
afreeman CreditAttribution: afreeman commentedI'm pretty sure what you're describing is default behavior for Drush. Unless you explicitly specify a version to download Drush automatically grabs the the recommended version.
Comment #5
MGN CreditAttribution: MGN commentedTry doing a clean install (don't install on top of an existing installation - remove all of the old files first, before unpacking the latest code) of the current 6.x-2.x code and the problem should go away. I don't think this is a bug, just a bad install.
Comment #6
penyaskitoDoing #5 worked for me, thanks!
Comment #7
lamp5