After upgrading to ctools 1.7 and panels 3.7, running update.php always resulted in the following error:

Panels cannot be updated because CTools 1.7 (API v1.7.2) is required. Please update CTools and then try update.php again.

This is after ctools had already been upgraded. I eventually realized that Drupal was not sufficiently bootstrapped and thus PANELS_REQUIRED_CTOOLS_API was not defined, causing the test to always fail. The attached patch fixed my problem.

CommentFileSizeAuthor
panels.panels_update_6310.patch869 bytesmvc

Comments

j0nathan’s picture

j0nathan commented

Marked #874710: Problem w/ update, now can't enable Panels/Ctools? as duplicate of this issue.

merlinofchaos’s picture

merlinofchaos commented

That's odd. During update.php the .module files are supposed to always be loaded. I don't understand why this would happen this way.

mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented

That was also my understanding, but I couldn't figure out why that wasn't happening as expected. I also see that at least one other person has had this problem, but if this affected everyone who was upgrading I would have expected a flood of duplicate issues in this queue, which doesn't appear to be the case.

That said, I don't think my patch would break anything for sites where the modules are loaded as expected.

edvanleeuwen’s picture

edvanleeuwen
Primary language Dutch
Location Waalwijk
commented

Confirming that this problem arose during upgrading CTools and Panels and that the patch solved the problem.

anne-pierre’s picture

anne-pierre commented

I am having the same issue. Will try the patch and let you know. thanks

Blooniverse’s picture

Blooniverse commented
Issue tags: +patch

My experience: 'Panels 6.x-3.7' works fine with the patch above -- NOT so 'Panels 6.x-3.x-dev' from 2010-Aug-24! BTW, will the patch above not find its way into the most current version of Panels?

merlinofchaos’s picture

merlinofchaos commented
Issue tags: -patch

Removing useless tags.

ebeng’s picture

ebeng commented

I'm having the same problem, but I'm really a novice. Could you be so kind is to tell me exactly where this patch should be inserted. I'm guessing it goes in the panels.module folder-- Like I say, I'm guessing.

Thanks for your help.

Regards, Eben

mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented

@ebeng: panels.module is a file. the patch above is for the file panels.install, which is located in the same directory.

please read http://drupal.org/patch/apply if you need help.

savedario’s picture

savedario commented

I had the same problem. The patch worked perfectly. Thanks a lot.

I updated 2 different sites and I didn't have the problem the first time.
The only difference was that the second time the update stopped with an (other) error and I had to retry before the issue with panels_update showed up.

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Fixed

Well. I'm uncomfortable with this patch because I just don't understand how we get into that situation.

That said, it doesn't appear dangerous to commit, since it's a very safe test, and appears to fix the problem for those experiencing it. I just wish I understood the problem better.

Committed to all branches.

ebeng’s picture

ebeng commented

MVC:

Thanks for your post. I learn something new every day. As it turns out, I brought up my problem at a local Drupal Meetup meeting and was persuaded to stay away from patches if at all possible because of the potential for problems when making future updates. I was queried about the steps I was using to do the Panels and cTools update. Generally I just delete the old version and replace it with the new version and run update.php. I was told that I needed to uninstall the modules before doing the update. So, I followed these steps and the update worked.
1. From each Panels configuration page on my site, select Export - to capture the panels configuration.
2. On my site Modules page de-select the Panels and cTools modules.
3. On my site Modules page, click on the un-install button and from the uninstall page select from the list to uninstall Panels and cTools. I understand that this wipes the database clean.
4. Delete the old versions and copy the new versions of Panels and cTools to my sites/all/modules folder (I use my host's cPanel to do this)
5. Back on the site run update.php
6. On my site Modules page, select Panels and cTools (of course in the order prescribed).
7. Then, going, in turn, to each panel page on my site I selected "edit", which took me to the Panels configuration page where I imported the panel that I had exported in Step 1, above.

Using this process, everything worked; although the process was a bit laborious.

I'm wondering if others are having this problem because they don't uninstall the modules before updating.

j0nathan’s picture

j0nathan commented

Hi ebeng,
Normally you should not need to uninstall a module to update it. Uninstalling it may delete all the configuration of the module and you don't want this.

mvc’s picture

mvc
they
Primary language English
Location Montréal, CA
commented

@ebeng as j0nathan says you should NOT uninstall modules before upgrading them. That will accomplish nothing but deleting all the settings for the module. However, deleting the old module directory before putting the new version into place is a good practice, since if you just copy over the files you will sometimes leave behind old files which have been removed in the new version.

As for patches, it's true that in general you should not apply them unless you know what you're doing. If you're not sure whether you know what you're doing, the answer is probably "no" :)

In this case, however, the module maintainer has mentioned that this patch has been accepted and will be part of the next version of this module (see comment #19 above) so it should be safe for you to apply this patch to your site if you have this problem and you can't wait for the next official release.

Status: Fixed » Closed (fixed)

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

shaneonabike’s picture

shaneonabike commented

I can confirm this patched worked for me :)

  • Commit e2ff1e3 on 7.x-3.x, master, pipelines, 7.x-3.x-i18n, 8.x-3.x by merlinofchaos: 
    #879482 by mvc: Ensure Panels and CTools module files are loaded during...