Walrus Posted October 4, 2015 Share Posted October 4, 2015 I just started the upgrade to 1.6.11 and noticed 1-Click is arching thousands of files that have nothing to do with Prestashop but are in the root of our server (i.e., belonging to other websites). Why is it doing it? I would expect it to know which files and directories belong to Prestashop, and which to ignore. Is this an oversight? It's now going to take hours to upgrade, or fail by consuming too many resources, when it should take a few minutes at most! Surely, our server isn't the only one that hosts more than one website. Are we expected to delete all of our other websites before using 1-Click? How are others who host more than one site coping? Link to comment Share on other sites More sharing options...
bellini13 Posted October 4, 2015 Share Posted October 4, 2015 I would just not use their backup option. Just perform your own backups, and disable that option. Do you really want to rely on Prestashop to properly backup your site, and then restore it when it does fail? Link to comment Share on other sites More sharing options...
Walrus Posted October 4, 2015 Author Share Posted October 4, 2015 (edited) Well, considering the module has been around for so many versions and regularly updated, I would expect it to work. First time I tried it, it destroyed my test store but I was able to roll back. I then installed another test store and using 1-Click took only 3--4 minutes to upgrade. It's now thrown internal server error and stopped!!! Edited October 4, 2015 by Walrus (see edit history) Link to comment Share on other sites More sharing options...
bellini13 Posted October 4, 2015 Share Posted October 4, 2015 obviously that's your choice, however I would never trust this upgrade module to also backup and restore my website and database. your track record should be evidence enough Link to comment Share on other sites More sharing options...
Walrus Posted October 5, 2015 Author Share Posted October 5, 2015 I tested 1-Click and it worked fine but that was on a test store installed in a directory (of course, I backed up the SQL data first). The first upgrade went belly up but I assumed module had been fixed. This time, I just happen to look when it started to archive another site which was in a folder beginning with 'K', so unless your other site or dir starts with A, B, C, etc, you are unlikely to connect the failure with lack of resources due to 1-Click trying to archive everything in the root! The reason I want to use 1-Click is so I don't have to install all of the modules again. As it is, it will take me maybe a week to find all of the customisations and to add them back. Configuration lists only 7 changed files. I know I have changed lots of templates but Configuration isn't listing any .tpl files. Link to comment Share on other sites More sharing options...
bellini13 Posted October 6, 2015 Share Posted October 6, 2015 Trust me when i say this, you will still have to re-install and re-configure modules and themes after the upgrade is complete. Don't expect this process to go flawless Just backup your own database and website content and disable the backup option in the module. Allowing the module to do it, can cause the process to timeout (depending on size of database and server content). Also, make sure you are doing this on a test copy of your store first, so when it fails, your live store is broken Link to comment Share on other sites More sharing options...
Walrus Posted October 8, 2015 Author Share Posted October 8, 2015 Ah, that's a shame if I have to reinstall the modules. I may as well just delete everything and install newest version. The database is pretty small. Sadly, 1-Click is dumb. It cannot tell what belongs to Prestashop, and what doesn't. In fact, there are only 38--40 files/folders that it needs to look for and archive (the subfolders will take care of themselves). It does this pretty well if you have installed in public_html/myStoreName but not if you install Prestashop in public_html/ I originally did install in a folder but it caused problems, so, reluctantly, I moved it to root. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now