A reoccurring issue we have run into is that people contact us looking to have software on their website upgraded because a problem with the website has started occurring. They fail to mention that at all, leading to them complaining that the problem hasn’t been fixed after the upgrade. It happens so much they we now note in description of our upgrade services that upgrading probably won’t solve a problem they are having, but that we can address the problems while doing the upgrade. We also specifically ask if they are having any issues with the website, in case they miss that note, so they can we avoid having unhappy customers.
We recently had an example of that sort of situation that deserves special note, because it could lead to serious problems. We had someone contact us looking for an upgrade of PrestaShop, where they were currently using the last version of PrestaShop 1.6. Upgrading any further means upgrading to PrestaShop 1.7.
Going from PrestaShop 1.6 to 1.7 sounds like a relatively minor upgrade, but it is actually a major upgrade. Existing themes and modules won’t work with the new version. So someone doing that upgrade trying to fix a problem is likely going to have new headaches to deal with in addition to the still unresolved problem.
PrestaShop doesn’t suddenly change how it is working. So if something starts going wrong, that means something else has changed. If server-level software changes, that could cause problems with PrestaShop that an upgrade could resolve. But other changes will not be resolved that way. For example, a hack won’t be resolved by upgrading and trying to upgrade when there is malicious code on a website could actually cause even more problems.
If you don’t know what is going wrong with your PrestaShop website, it is best to find help to fix the problem instead of guessing at a fix, like doing an upgrade, and hiring someone to do that. If you do need PrestaShop support, we are there to help.