modules not upgrading properly since 6.1.0

[keitaro]

Hello,

 

title wrong meant 1.6.1.0

 

I have an issue where some modules keeps saying they need updating.

 

I update it says updated. the module list shows the newest version but still the modules auto check says x module needs updating.

 

i tried checking the permissions of the modules in question and updating them manually but same issue.

 

Anyone seen this before or know what might cause it.

 

Only some do do this.

 

I spoke to the dev of 1 and he gave me a newer not yet released version higher than the current one but still it says update available.

 

 

thanks for any help or suggestions.

Edited July 29, 2015 by keitaro (see edit history)

[kisjani0]

Greetings Keitaro,

 

have you been able to solve this issue? I'm having the exact same problem 1.6.1.11.

The modules page keeps saying for some modules that they need update, but when I click the update it says all updated, but nothing happens, it still keeps saying there is an update for those modules.

Your help is mostly appreciated.

 

Thanks in advance.

[bellini13]

Can you be more specific... are these custom modules that you have purchased?

 

Perhaps they do have updates, and you are not entitled to update them

[kisjani0]

bellini13, thanks for your reply.

 

I don't think that this is the problem.

It seems like these are modules like gsitemap and dateofdelivery. This happens after an upgrade from 1.4.

After the upgrade I can update a few modules immediately.

And then after 1-2 days I log in and I'm able to update some of those modules or sometimes all of them.

This also indicates that the issue is not that these are paid modules.

(I have ran the upgrade already several times.)

I would like to update all these modules rather immediately after the upgrade in production.

 

No errors in the logs or similar.

Edited January 31, 2017 by kisjani0 (see edit history)

[bellini13]

have you noticed in the modules folder on the file system, after you try to upgrade the modules, do the timestamp on those modules files/folder change?

[keitaro]

The issue is likely 1 of 2 things.

 

1 as listed already. Prestashop is a bit dumb it tells you there's an update to a module you might have purchased privately from the developers site rather than prestashop add-ons.

 

So it tells you there is an update (which there is) but because you didn`T buy on presta it says successful but it actually failed due to not actually owning on presta add-ons.

 

You already confirmed this is not the case.

 

2. The permissions in the modules folder is wrong some where.

 

Either the default /modules is set wrong or the individual module /module/modulename is set wrong if only certain modules are failing.

 

best solution is to go into file zilla

click the modules and set permission correct and choose all sub files and folders. + this time only or to your preference

 

Grab a coffee come back and test updating.

 

There are faster ways to change all permissions but coffee time!

 

 

 

Make sure you clear all cache too in the performance folder.

[kisjani0]

Thanks for all the help here.
After several nights spent with this I now finally figured out that some weird custom language setting caused this whole issue.

I had to enable English language and set the language of the upgrading user to English.

After that all modules were updated as expected.

Edited January 31, 2017 by kisjani0 (see edit history)