Rollback feature for shopware Update
In support tickets and in various forums you often read about problems with Shopware updates. It is not uncommon for the store (frontend and admin) to no longer be accessible after an update.
To avoid destroying the entire store or the customer's test environment, the update should check the accessibility of the frontend/admin at the end. If, for example, the browser returns an error 500, a rollback should be triggered to restore the store to its previous state.
Currently, the customer is often faced with an unsolvable problem in this case and loses a lot of time until the store works again.
Benjamin Hummel
shared this idea
-
Benjamin Hummel
commented
It doesn't necessarily have to be a rollback function. But errors caused by extensions, for example, must not have such an impact as has been the case for a long time, which affects new shopware customers.
-
Benjamin Hummel
commented
The topic of “problems with updates” (entire store destroyed) is a recurring theme in many support tickets and also in discussions with major customers and needs to be addressed. In my opinion, this is one of the biggest pain points.
Of course, this will probably be a big issue when it comes to implementation, but the announcement alone would restore a lot of confidence in the product.
Some agencies no longer recommend Shopware because the update processes are so opaque and costly.