Hello.

I seem to be unable to update to 6.4.0 successfully. Is there any special instructions for this version? I successfully patched to the 6.3.9 version not that long ago, however this seems to elude me. I've had to put the support request in for 6.3.9 as I can't make it do 6.4.0.

Comments

Letharion’s picture

Letharion commented

The version that you are describing does not exists. Do you mean 6.x-3.10, or have you posted to the wrong issue queue? There is nothing special about this upgrade. What is your problem?

musojon74’s picture

musojon74 commented
Title: Problem updating to 6.4.0 » Problem updating to 6.x-3.10
Version: 6.x-3.9 » 6.x-3.10

Hi Letharion.
I'm so sorry, I can't read numbers apparently. Yes upgrading to 6.x-3.10, all that happens is that the upgrade confirmation screen comes up (saying you can proceed happily to administration). However the version is still listed as 6.x-3.9, and the red warning for security patch is still present. So it looks like the upgrade has not happened.

Letharion’s picture

Letharion commented

What does the version number in the info-file say?

musojon74’s picture

musojon74 commented

It has version 6.x-3.10, core 6.x.

Letharion’s picture

Letharion commented

Where does it still say that panels is 3.9? Could it be that you have more than one panels module, such as one in sites/all/modules and one in sites/example.com/modules? Have you run update.php?

musojon74’s picture

musojon74 commented

Thanks for looking. There's only one panels module in the /var/www/sites/all/modules directory, it's not duplicated in the /var/www/modules one.

Yes, ran update.php. Did the same routine I did only a few weeks back to push to 3.9, no problems then. It's bizarre.

--edit sorry it says it's still 3.9 in the available updates screen, in red, with recommended - security update - 3.10

Letharion’s picture

Letharion commented

Sorry, the only reason I can come up with for Drupal to list the old version number when the new is in the info file is if you have two version of the file and confuse Drupal that way somehow. I don't know what other advice I can give.

Letharion’s picture

Letharion commented
Title: Problem updating to 6.x-3.10 » Core doesn't recognize Panels being updated from 6.x-3.9 to 6.x-3.10
merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

Be sure to clear caches. Go to your update status page and refresh its data. There's really not much the module can do about this, though; this is completely Drupal core functionality. I've no idea why it does this sometimes. But if the .info file says you're running the correct version, then you are.

aerodub’s picture

aerodub commented

same issue I did everything as usual but drupal keeps the same update status regarding panels.

musojon74’s picture

musojon74 commented

Deleting the panels folder from my dev site, then update.php, then readding the 3.10 version, seems to clear the problem.

musojon74’s picture

musojon74 commented

OK this is entirely my fault, I couldn't see the wood from the trees yesterday. The module version I installed was 3.9 again. I can only apologise for wasting time on this I will install modules early in the morning from now on.

alreaud’s picture

alreaud commented

Interesting... I have three sites. One is the main site, with the modules at /sites/all/modules. Then for the other two sites, I do a symbolic link so that regardless of what the actual document root path is, all sites point to the same modules directory.

I'm operating in off-line mode, cleared caches.

On site one, I performed the update to Panels 6.x-3.10 and it worked correctly. On sites two and three, however, the update does not appear in the updates. This makes me wonder if there is a hard flag that gets changed in the code that indicates an update has been performed. Looking in /update.php?op=selection, I don't see a Panel Module update on sites two and three.

In /admin/build/modules, site one shows Panels 6.x-3.10, sites two and three show Panels 6.x-3.9. The problem indicated above by musojon74, the wrong upload, can't be occurring, because there is only one file set, and one database does indicate the correct version.

I mirror this configuration on a testing server and the problem has replicated. Maybe this occurs only on multi-sites? Or is it related to the symbolic linking?

merlinofchaos’s picture

merlinofchaos commented

The update module caches all the versions it uses, because figuring out version numbers for projects is very expensive, unfortunately. So this cache does need to be cleared.

merlinofchaos’s picture

merlinofchaos commented

And other than that, the only 'hard' coding is what's in the .info file.

alreaud’s picture

alreaud commented

Update: Problem explained, LOL. Many moons back, it appears that the above configuration of symbolic linking would not work for the Panels Module. The symbolic linking of core and and add-on modules was done to save space on the server. So on my three sites, sites two and three symbolically link all modules EXCEPT Panels.

FTP upload of the Panels 6.x-3.10 module update to the individual site modules folder fixed the problem.

Sorry for the confusion, merlinofchaos, it's been a while since I had to look at Panels, and hence forgot that detail. My problem is therefore actually fixed by #7, problem resulting from wetware error...

Status: Fixed » Closed (fixed)

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

isunzzy’s picture

isunzzy commented

There may be more than one Panels folder. I have met the same problem and fixed.