Reputation: 2315
Some modules can be auto-updated in backoffice by clicking the update button. However if the module is from an other source than prestashop itself (e.g. github) the module needs - afaik - to be updated manually.
So how should one handle updates?
Download ZIP and
unzip
it over the corresponding modules folder (/modules/acme/
)rsync
it to /modules/acme
(rsync -trv /tmp/acme /modules
)--delete
rm -rf /modules/acme
and cp -a /tmp/acme /modules/acme
Side note: what about the config.xml and possibly other generated files?
Same applies for theme updates, how to handle these?
Concerning current version Prestashop 1.7+.
Upvotes: 0
Views: 4375
Reputation: 31
You can perform the upgrade automatically with this free module https://www.prestashop.com/forums/topic/820013-migrate-or-upgrade-prestashop-16-or-other-versions-to-17-%E2%80%93-free-module/
Hope it helps
Upvotes: 0
Reputation: 4337
If the module upgrade is made correctly (you can check if module version is updated in main module class constructor and uses upgrade scripts in upgrades
folder and files inside the module) you can unzip over it. Then visit the modules list page in backend and module upgrade will run. config.xml
is auto (re)generated and used only for optimizing module list loading in the same backend page - it has no effect on module behaviour itself.
For themes you can also just unzip over the last one.
When I am in doubt with any upgrades I make a development copy of the store and do upgrades there first and see if everything is ok then do upgrades on live instance.
Upvotes: 1