Upgrade to v 1.0.2

[netamismb]

I am currently in process to migrate from prestashop 1.6 to thirtybees. After migration I use the module tbupdate to update from 1.0.1 to 1.0.2. Something is strange as i get way to more files to be backup: Analyzing the situation...Shop deactivated. Now downloading... (this can take a while) Download complete. Now extracting... File extraction complete. Now backing up files. Backup files in progress. 1438080 files left. Backup files in progress. 1437680 files left. Backup files in progress. 1437280 files left. Backup files in progress. 1436880 files left.

[Occam]

I can confirm this. Try to backup manually first and then start the upgrade with deactivated backup.

[vzex]

Same, let my backup run over night since it never ended!

Update/rollback seemed to work perfectly a month or so ago, seems something has changed.

Finally cancelled the back up next morning thought it was backing up entire host with all those files! :)

Found the backups I didn't think were made in admin>autoupgrade>backup but have not checked yet if they are complete.

They do not show up in rollback.

For now I'm using cpanel to compress my shop and save as a zip file along with php admin and TB to save the database then download to desktop.

At least I hope it is backed up, haven't tried a restore yet!

Wish there was a quick and easy way to do this automagically in TB!

There isn't anything more important than a backup!

[alwayspaws]

@netamismb Please see this discussion, which has some new info:

https://forum.thirtybees.com/topic/693/migration-module-wants-to-install-1-0-1/3

[Occam]

@alwayspaws Sure there are a lot of bugs left in 1.0.2 , but this applies even more to 1.0.1. Honestly, I wouldn't launch a live shop before release 1.1. But testing is necessary for every release.

[Guest]

@Occam I'm planning on making one of my stores live on 1.0.3 if it does everything I need it to do for quantity discounts on combinations. This is because I'm stuck with my main store on PrestaShop 1.6.1.11, which has loads of problems and each version upto 1.6.1.16 since then has gotten worse; I tried out 1.6.1.16 last week on a copy of the store as we really needed some of it's fixed features but it was a disaster! Each version seems to get more and more broken - the problem is people fix one problem and don't test the impact of the code changes in the wider scope so break a myriad other things in the process. The fix I now need isn't earmarked till 1.6.1.18 and .17 isn't even out!

We've come to the conclusion that PrestaShop 1.6 is now FUBAR and it's no longer possible to upgrade to a later version. It really feels like PrestaShop don't care about it and are letting anyone submit untested fixes just so they can say 'we've fixed over 20 things this patch'. For this reason we're going TB 1.0.3 earlier than anticipated but feel it's a safer path to get our store bedded in ready for the Christmas promotions.

[spidawebs]

I can confirm this problem still exists. I've just upgraded to 1.0.3 and the backup files doesn't work. It says there are millions of files to backup and takes forever. We will just have to disable it until it is fixed.

@DavidP that's exactly what I am doing but I never dared to go past 1.6.1.2 after all the previous problems of upgrading. Lesley fixed most of the problems to give me a relatively stable shop but I have so many fixes that migrating to thirty bees is a real problem - all the problems are carried over. The only way for me to do it is to do a fresh install and then manually move across the customers, products and orders etc. I have a couple of other shops running successfully on fresh installs of thirty bees but migrating from prestashop isn't as good unless you have no third party modules.

[DaoKakao]

Perhaps this backup script could be useful for someone. It makes backup of /etc, root of /www, dumps all mysql databases as text and also mysql binary files within the mysql binary logs. ```

!/bin/bash

echo "========= !!! Should be ran manually as root !!! =========="

BKDATE=date '+%F' BKTIME=date '+%Hh%Mm%Ss' BKTIME1=date '+%T'

BKDIR="./backups/full"$BKDATE""$BKTIME.backup

BKDIR="/var/backups/full"$BKDATE""$BKTIME.backup

BKLOGFILE="/var/log/backup"$BKDATE""$BKTIME1".log"

echo "Starting backup at date:" $BKDATE"; time:" $BKTIME1"; backup dir: "$BKDIR 2>&1 | tee -a $BKLOGFILE echo "==================================================================================================================" 2>&1 | tee -a $BKLOGFILE

#######echo "Starting backup at "date '+%F %T' 2>&1 | tee /var/log/backup_date '+%F_%T'.log

echo -n "Creating directory" $BKDIR 2>&1 | tee -a $BKLOGFILE mkdir -p $BKDIR if [ $? -ne 0 ]; then echo " ... FAIL! Error code:"$? 2>&1 | tee -a $BKLOGFILE exit 1; else echo " ... Ok" 2>&1 | tee -a $BKLOGFILE fi

addin' self-copy of this script to backup

cp ./backup-all.sh $BKDIR/backup-all.sh

cd $BKDIR

echo -n "Backing up /etc ... " 2>&1 | tee -a $BKLOGFILE

#######read -rsp $'Press any key to start...\n' -n 1 key

tar -cjvpf $BKDIR/etc.tbz2 /etc if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo "Backing up webroot home dirs ... " 2>&1 | tee -a $BKLOGFILE

######read -rsp $'Press any key to start...\n' -n 1 key

echo -n "Trying to stop NGINX ... " 2>&1 | tee -a $BKLOGFILE systemctl stop nginx if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 1; fi echo "Ok, NGINX stopped" 2>&1 | tee -a $BKLOGFILE

echo -n "Compressing weboot dirs ... " 2>&1 | tee -a $BKLOGFILE tar -cjvpf $BKDIR/www.tbz2 /home-of-your-www if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE systemctl start nginx if [ $? -ne 0 ]; then echo "\nFailed to start NGINX! Error code:"$? 2>&1 | tee -a $BKLOGFILE exit 2; fi exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo -n "Backing up mysql/mariadb database as text ... "

######read -rsp $'Press any key to start...\n' -n 1 key

here you can add specific mysql user who have enough rights to make database dumps

mysqldump -uroot -pxxxxxxxxxx -A | bzip2 > $BKDIR/alldatabases.sql.bz2 if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE systemctl start nginx if [ $? -ne 0 ]; then echo "\nFailed to start NGINX! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 2; fi exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo "Backing up mysql binary files ... "

This is redundant, but could be the last resort whel restoring

#####read -rsp $'Press any key to start...\n' -n 1 key

echo -n "Trying to stop Mysql/Mariadb ... " 2>&1 | tee -a $BKLOGFILE systemctl stop mariadb if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE systemctl start nginx if [ $? -ne 0 ]; then echo "\nFailed to start NGINX! Error code:"$? 2>&1 | tee -a $BKLOGFILE exit 2; fi exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo -n "Compressing binaries ... " 2>&1 | tee -a $BKLOGFILE tar -cjvpf $BKDIR/alldatabases-bin.tbz2 /var/lib/mysql /var/log/mysql if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE systemctl start mariadb if [ $? -ne 0 ]; then echo "\nFailed to start mysql/mariadb! Error code: "$? 2>&1 | tee -a $BKLOGFILE fi systemctl start nginx if [ $? -ne 0 ]; then echo "\nFailed to start NGINX! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 2; fi exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo -n "Trying to start Mysql/Mariadb ... " 2>&1 | tee -a $BKLOGFILE systemctl start mariadb if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE systemctl start nginx if [ $? -ne 0 ]; then echo "\nFailed to start NGINX! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 2; fi exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

echo -n "Trying to start NGINX ... " 2>&1 | tee -a $BKLOGFILE systemctl start nginx if [ $? -ne 0 ]; then echo "FAIL! Error code: "$? 2>&1 | tee -a $BKLOGFILE exit 1; fi echo "Ok" 2>&1 | tee -a $BKLOGFILE

this for ease access from (s)ftp / scp

change to whatever you want or remove if not necessary

chown -R backupoperatorusername:backupoperatorgroup $BKDIR echo "======= !!!! ALL DONE !!!! =======" 2>&1 | tee -a $BKLOGFILE ```

[Traumflug]

File extraction complete. Now backing up files. Backup files in progress. 1438080 files left. Backup files in progress. 1437680 files left.

Being curious on this I counted files in my developer installation: sh $ find . | wc -l 81809 This is with just demo data installed, but with .git and node_modules (for theme development). A regular installation should have some 63'000 files only, plus 10 picture files for each product.

@netamismb, do you have more than 100'000 products installed, perhaps?

[DaoKakao]

@mdekker already said in the parallel topic, that backup feature builtin the updater module is non-functional, and should not be used

[DaoKakao]

@mdekker Sorry, it seems i misunderstood you