Update to 2.0.14 successful then white/blank screen

[aegersz]

Nodaz, i think you got into this mess by not restoring your database at the same time you restored your files.

if so, can you possibly go back and restore the 2 in sync ?

both the files and DB must be handled as one unit for most recovery operations.

of course, i could be wrong.

[Sir Osis of Liver]

It isn't necessary to restore the database when reverting from 2.0.14 to 2.0.13, whether uninstalling the patch with package manager, or restoring the package backup.  This was a one-off, didn't have access to the account first time, now it's happened again.  Don't know what causes the glitch, but uploading clean 2.0.14 files should fix it.

[aegersz]

no, i meant that if he installed 2.0.14 and then restored some files only (from when the system was a 2.0.13) then the DB says that 2.0.14 is on but it isn't, hence possibly causing unpredictable issues.

or am i confused ?

[Sir Osis of Liver]

The _settings table contains smfVersion, but it apparently is ignored.  On my three forums running 2.0.13 and 2.0.14, the smfVersion value is 2.0.1, 2.0.2, 2.0.7.  index.php contains -

Code Select Expand



     $forum_version = 'SMF 2.0.14';



but that reverts to .13 if patch is uninstalled or backup is restored.

[Arantor]

So in the Packages folder you have two copies of 2.0.14, one of which can be deleted.

[Nodaz]

So in the Packages folder you have two copies of 2.0.14, one of which can be deleted.

Ok so i deleted one of them.
Now when i go to package manager and try to uninstall i am told
"Cannot find Package ! "
there is still an instance of 2.0.14 showing in "browse packages"

EDIT:
i went back and the second instance is now there again...
SO, i go to installed packages and try to uninstall and now get :

This package cannot be uninstalled, because there is no uninstaller!

Please contact the mod author for more information."

Again

I dont understand why that happened.  Whe i look at the files in both instances it indicates they are both:

Files in archive smf_patch_2.0.14.tar.gz:

    package-info.xml (1629 bytes)
    proxy.php (5054 bytes)
    readme.txt (1474 bytes)
    smf_2-0-14_patch.xml (74005 bytes)
    Sources/Class-CurlFetchWeb.php (10954 bytes)


What is the simplest way to resolve this?

[Sir Osis of Liver]

Just upload 2.0.14 upgrade package, that should fix it.  And, yes, you'll have to reinstall mods.

[Nodaz]

Just upload 2.0.14 upgrade package, that should fix it.  And, yes, you'll have to reinstall mods.

So i downlaoded the package from the downloads page, then tried to upload it through the package manager and got this:


If i FTP in the packages folder i see this:

[Sir Osis of Liver]

You can't do that with package manager.  You have to upload the files using ftp client or your host file manager.

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

[Nodaz]

You can't do that with package manager.  You have to upload the files using ftp client or your host file manager.

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

I just edited with a shot of my FTP, should i delete anything 2.0.14 related in the Packages folder before i start?

[Nodaz]

You can't do that with package manager.  You have to upload the files using ftp client or your host file manager.

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

That link sends me to the download page for 2.0.13 i am presuming i should navigate to and find the large upgrade for 2.0.14?
The instructions seem to indicate i should be downloading and refreshing the current version.

[Sir Osis of Liver]

Don't worry about /Packages files, uploading clean set of files has nothing to do with packages, other than that it removes all installed mods and gets you back to a clean install.

The wiki article needs an update.  Click the 'Download' link top of this page, it'll take you to 2.0.14 downloads.

[Nodaz]

ok, thanks for you patience>  should i dowmnload/upload the zip or the tar, i presumme to the Public_html folder?
Then extract that file in place and it will overwrite everything there?

Then this has me a little flumoxted:
Extract the archive to the forum's directory, making sure that you delete upgrade.php and all the upgrade-x.x.sql files, and overwrite index.php, the sources folder, and the themes folder. You can either use FTP or cPanel's File Manager. On your forum, if you have replaced the standard smiley files with your own and/or replaced the standard avatar files, you might want to refrain from uploading both the smileys and the avatars directory. Important Note: If you carried out the optional step, you should also upload the sources from the large upgrade archive before you reinstall any custom themes.
do i need to run anything after unzipping?

then delete those files after unzipping?

[Sir Osis of Liver]

/public_html is your forum root, all of the directories/files in the upgrade package have to go there.  I've always downloaded the zip, unzipped, and uploaded everything via ftp.  Don't know what happens if you upload the zip and use file manager to unzip it in place, would guess you'll get a prompt whether you want to overwrite or not.  You don't need the upgrade scripts, they are used to upgrade the database, which is not necessary in your case, and they pose a security risk if left on the server.

[Nodaz]

/public_html is your forum root, all of the directories/files in the upgrade package have to go there.  I've always downloaded the zip, unzipped, and uploaded everything via ftp.  Don't know what happens if you upload the zip and use file manager to unzip it in place, would guess you'll get a prompt whether you want to overwrite or not.  You don't need the upgrade scripts, they are used to upgrade the database, which is not necessary in your case, and they pose a security risk if left on the server.

Ill upload them directly via FTP:


Ok Also here is a Screen Shot of my Public_Html directory, do you see anything there that can/should be be deleted (maybe left over from stuff)<
Im presuming extracting the archive will overwrite most files but leave stuff that is already there and not replaced)

[Sir Osis of Liver]

Assuming you already have good backups of all your files and database, I wouldn't delete anything unless forum had been hacked, just upload the clean files.  Anything left over from previously installed mods (looks like you have a gallery) won't cause any problems.  The database will still contain data/tables added by mods.  If you don't reinstall a mod, the data is ignored; if you reinstall a mod that's added stuff to the db (i.e., gallery), it should pick up where the previous mod install left off, so you don't lose anything.

[Nodaz]

Assuming you already have good backups of all your files and database, I wouldn't delete anything unless forum had been hacked, just upload the clean files.  Anything left over from previously installed mods (looks like you have a gallery) won't cause any problems.  The database will still contain data/tables added by mods.  If you don't reinstall a mod, the data is ignored; if you reinstall a mod that's added stuff to the db (i.e., gallery), it should pick up where the previous mod install left off, so you don't lose anything.

Very good, thanks
I have backups through my host, but am going to run backups manually, download copies via FTP and  through the forum as well.

[Nodaz]

Assuming you already have good backups of all your files and database, I wouldn't delete anything unless forum had been hacked, just upload the clean files.  Anything left over from previously installed mods (looks like you have a gallery) won't cause any problems.  The database will still contain data/tables added by mods.  If you don't reinstall a mod, the data is ignored; if you reinstall a mod that's added stuff to the db (i.e., gallery), it should pick up where the previous mod install left off, so you don't lose anything.

SUCCESS !!
FTP upload resulted in a working version of 2.0.14>
Thank you all for the help !