I just updated my site from 7.50 to 7.54. After the update, I ran the Available Updates report which showed that the site was at 7.54. Looking at the rest of the report, I saw that ctools needed updating from 7.x-1.10 to 7.x-1.12, so I downloaded that and rolled the new version into the modules directory. I then ran update and it told me there were 2 updates, so I proceeded. I then got the message:

Fatal error: Cannot redeclare page_manager_page_menu() in /var/www/bin/drupal-7.54/sites/crimefiction.org/modules/ctools/page_manager/plugins/tasks/page.admin.inc on line 15

I then went back to the tab where I had run the Available Updates report and refreshed to see what state ctools was in. That gave me:

The crimefiction.org page isn’t working

crimefiction.org is currently unable to handle this request.

I then went back to the shell, removed the ctools directory in modules and replaced it with 7.x-1.10.

But, the site is still in the same shape.

Now what?

I have posted this on the main forum as well, but am posting it here because ctools seems key to the problem.

Comments

tamhas created an issue. See original summary.

darrenwh’s picture

darrenwh commented

Hi,
Have you tried running a registry rebuild?

rivimey’s picture

rivimey
she/her
commented

@tamhas the registry rebuild idea is good - it is a drush command that you can download using drush but should not be included in the site itself.

If that doesn't work, I would guess you now have two copies of ctools included in the site. If you're on Linux/Mac, try:

find $DIR -type d -iname ctools -print

Replace $DIR with the Drupal site's root directory, the one containing index.php. It should print the path name of all directories called ctools, and I would hope to see only one path. If there is more than one you will need registry rebuild too: firstly move one version out of the way - outside the website tree entirely - and then run registry rebuild (drush rr) on the site. That should update the paths in the database to match the current location of all modules, and in doing so get the site working again.

Hope this helps.

tamhas’s picture

tamhas commented

The core problem here turned out to be that usually I install modules under sites/all because we have multiple sites running off the same code base, but for some reason this time I installed the update under sites/ which got things confused. Cleaning up the installs and a registry rebuild did solve the problem. Since the exchange about this was on the main forum, I forget about the post over here. But, all fixed now! Thanks all.

rivimey’s picture

rivimey
she/her
commented
Status: Active » Closed (works as designed)

Thanks.