I don't think 2.0.13 upgrade completed successfully - now what?

Started by samd, April 10, 2017, 10:01:47 PM

Previous topic - Next topic

samd

I upgraded from 2.0.12 to 2.0.13 recently, and the result was that my Webtrees ended up in maintenance mode.

I searched and found the answer to that, and got it out of maintenance mode, but I don't think the upgrade completely successfully. When I run ADMIN|Maintenance|Routine|Check all files against current versions, the result is ?? in the Current Version column for every file.

It does show the SMF Version as 2.0.13, and it shows a version number for all files under the Your Version column, but I'm pretty sure it previously would show the current version number of each of the files under the Current Version column.

The files that show they are 2.0.13 are:

LogInOut.php   2.0.13
PackageGet.php   2.0.13
Subs-Post.php   2.0.13
Subs.php   2.0.13
Themes.php   2.0.13

Since under the Current Version all I see are double question marks, I can't tell if there are files that should have been updated that weren't.

So, am I  missing files that should have been updated with the update to 2.0.13?
And if I am, how do I fix this problem?

When I ran the SMF 2.0 Repair Settings tool, I received the following message:
"Some settings are not being shown because the database connection information is incorrect.
Check your database login details, table prefix and that the database actually contains your SMF tables."

I have verified that the MySQL database files and tables do exist and Webtrees is pointed to find them where they are located on my server, and that Webtrees and the MySQL database use the same login details and table prefix.

Thank you.





Bob Perry of Web Presence Consulting

Assuming you did the upgrade by clicking the patch method link in the package manager screen, you can be double sure everything is kosher by redoing the upgrade manually uploading the files and folders out of the large upgrade .zip file from this sites download directory, then navigating to the upgrade.php with your browser and execute instructions... if you are planning to use SMF long term it would behoove you to learn this process, the only negative drawback of this is that you will have to re-install all the third party modules that you want to carry forward with.

Best Regards,
Bob Perry



"The world is moving so fast these days that the man who says it can't be done is generally interrupted by someone doing it." Elbert Hubbard

Illori

the correct process to follow is here https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files if you want to use the large upgrade package.

not all files will show 2.0.13 version, only those that were changed in the 2.0.13 patch will show that version.

Kindred

So, the ?? Showing in tge current version column just indicates an issue with connecting to smf, not an issue with your install
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

samd

I installed the new version via something in the program that indicated the new version had been released. I don't recall if that was a link when I started it, or something in the Maintenance area. Thank you, Bob Perry. Having to reinstall the third party modules will be a pain, if that means redoing the menu from scratch.

Thank you, Illori, for the link. I'll read that through, though I'm disinclined to change any files until I know what files were changed by the 2.0.13 upgrade.

And thank you, Kindred, for explaining why the ??. Is there some reason why my installation would have trouble connecting to SMF now, when it didn't before I upgraded to 2.0.13, or is there something I can do, some file I can edit, that will enable connecting to SMF? Insofar as I'm aware, nothing on my server has changed since before I upgraded, and my installation was able to connect to SMF before the upgrade. So is there some way to fix this problem of not connecting to SMF? My site isn't large and has just a handful of users, but I would like to make sure that it's up-to-date at all times, which sort of requires being able to see which files might be out of date.

Thank you.

Kindred

no, it really doesn't require searching files out of date...    although that's a nice feature, as long as you have the current patch installed, you should be good... and that version check will not affect the running of your system, at all.

As for what changed...   might be the recent change here to use SSL.
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

samd

Could I set up a new server that's the SMF server? If so, what URL would I use?

Thank you.

samd

I solved the issue. I ran repair_settings.php again, which showed no errors, and looked closely at the file paths. I noticed the first file path was an https to my forum directory, and it recommended http, so I changed that, saved, exited and deleted the repair_settings.php file.

Now I get the latest SMF newsletter, as well as in Maintenance | Routine, it shows the current version of files for SMF.

So everything is back to normal, I think. I haven't done a manual update

Thank you all for your assistance.

Kindred

except, if you have a certificate, you really really want your site to be https
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

samd

Well, it IS still https. I can access it via https. In Admin | Configuration | Server Settings | Database and Paths, it still shows the path as https.

So when I changed the path to http in repair_settings.php and saved it, whatever file it saved that change to is the one that made the difference. That didn't change anything in my installation of Webtrees where paths are shown.

I haven't looked at the files on the server to see which file(s) changed, or the PHP file to see what it writes to, but I'll do that within the next couple of days to see which one it was.

I think I also set Queryless URLs to OFF, as that had no value, so had not been set one way or the other before.

And I've just realized that throughout this discussion I've used the term "Webtrees" when I meant SMF. So everywhere I've mentioned Webtrees, it should have been SMF. My sincere apologies. I have SMF in a directory under my Webtrees directory, so I kept seeing the name Webtrees, and was so intent on trying to resolve the issue, I didn't realize I was making the mistake of misnaming the program.

Advertisement: