Started by LandyVlad, Feb 01, 2021, 11:50 PM
0 Members and 1 Guest are viewing this topic.
Quote from: Skhilled on Feb 04, 2021, 03:31 PMWhen you say using the patch, do you mean using the upgrade in the admin? Or do you mean using the large upgrade patch found here?https://download.simplemachines.org/If using the admin patch there has always been issues with that for MANY years but the team refuses to acknowledge them. It is always best to use the large upgrade package...unless there's a problem with that.
Quote from: Ronald on Feb 04, 2021, 04:09 PMYes after we finished doing the Beta Testing, they decided to release 2.0.18. Yes the patch is what I am referring to. Yes there also is a large upgrade available also.. This patch is a huge piece of updating.I had a beta test board, the patch worked great, I also did my smf arcade site, used the patch and no problems at all, went right in.Then I decided to use the patch on the senior forum, ooooopsss lots of errors, so I went to smf support reported it and we tried to figure it out, then all others started to post there errors when updating with the patch..Haven't done anything as yet, probably remove all the mod.'s first then try. But again a lot of the mod.'s are outdated, and probably will not go back in..
Quote from: shawnb61 on Feb 04, 2021, 07:44 PMSame is true for those mods with 2.0.16 conflicts. I fixed the packages. I shouldn't have to do that, though - the mod authors need to do that.
Quote from: LandyVlad on Feb 02, 2021, 11:27 PMAs in uninstall all mods and then upgrade and then reinstall?An issue I'd experience there is that I get errors when attempting to remove quite a few of the mods.
Quote from: LandyVlad on Feb 05, 2021, 05:52 AMWill taking that action as described delete all the settings for the mods? As I really want to keep those (for example, threads which have a thread prefix using that mod, I want to keep the prefixes there, etc)
Quote from: LandyVlad on Feb 05, 2021, 05:52 AMAlso when you say install mods do you mean that I'd also have to install the previous interim upgrade packages?At the moment I have the installed interim packages showing in my package manager from 2.0.12 onwards.
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMThe way the mods install etc is very clumsy and I presume that increased use of hooks will get around this? Perhaps? As for what order I've installed mods in. what with updates and all - I haven't a clue !
Quote from: LandyVlad on Feb 10, 2021, 06:10 AMI have that mod but didn't think it was always accurate. (check out 25 and 26 for some weirdness as an example)
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMThe way the mods install etc is very clumsy and I presume that increased use of hooks will get around this? Perhaps?
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMAs for what order I've installed mods in. what with updates and all - I haven't a clue !
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMAlso given that I am currently running 2.0.17 can I delete the previous upgrade packages, and if so should I uninstall them first or just leave alone and simply delete from package manager without uninstalling?
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMLastly - what's the easiest way of duplicating a forum including databases etc but with new database names so there's no confusion between old and new forums.
Quote from: LandyVlad on Feb 09, 2021, 03:31 AMAnd what's the best normal backup process?
#!/bin/sh## User configurationHOMEDIR=/blah/blah/public_html/blahCRONDIR=/blah/blah/cronjobsFSBU=blah_fsbu.tarDBBU=blah_dbbu.sqlLOGFILE=$CRONDIR/blah-backup.logFTPHOST=ftp.yadayada.comFTPUSERemail@example.comFTPPW=guessmeFTPDIR=/backupsDB=blahblahDBUSER=yadayadaDBPW=yada1## Clear old logrm $LOGFILE## all output to logfileexec &> $LOGFILE## head over to target dir to capture all output in one placecd $CRONDIR## db backupmysqldump -u$DBUSER -p$DBPW --hex-blob $DB > $DBBU## file system backuptar -cvf $FSBU $HOMEDIR## ftp to other site for storageftp -n $FTPHOST <<END_SCRIPTquote USER $FTPUSERquote PASS $FTPPWbinarycd $FTPDIRput $FSBUput $DBBUquitEND_SCRIPT## delete the filesrm $FSBUrm $DBBU#
Page created in 0.098 seconds with 28 queries.