Upgrading from 2.0.17 to 2.1.14 not going through

[StarredSkies]

While running the upgrader, I am stuck at 14% with the error 'Server has not responded for 30 seconds. It may be worth waiting a little longer before trying again.Click here to try again.', despite waiting some time.  This upgrade is being done in English (referring to previous upgrade issues).

'Executing database changes
Please be patient - this may take some time on large forums. The time elapsed increments from the server to show progress is being made.
Executing upgrade script 1 of 2.
Executing: "Changing column names." (1 of 41 - of this script)'

I tried changing the limit in upgrade_2-1_mysql.sql and have had no luck. (My host is also not GoDaddy and they have been wonderful in helping me with this issue.)

This is also on a subdomain for testing an ACTUAL 2.1 upgrade for my website. (Could this be a database routing issue? It seemed to link up fine. Host confirmed password is correct.)

This is where I am stuck. Am I doing something wrong? Any advice would be helpful. Thank you.

[StarredSkies]

Update: My host attempted to fix the issue (they're amazing) but had no luck. They tried on my main and sub domain. Both encountered the issue.

My first attempt was done without upgrading to 2.0.19, while the host's second attempt was done after upgrading to 2.0.19 (and fixing out of date files with repair_settings.PHP). Obviously, both failed.

One error that came up for them was:

Code Select Expand

Fatal error: Uncaught Error: Call to undefined function httpsOn() in /home/DOMAIN/SUBDOMAIN/upgrade.php:285 Stack trace: #0 {main} thrown in /home/DOMAIN/SUBDOMAIN/upgrade.php on line 285Hence the upgrade is missing some files. Strange.

So I'm at a loss.

[Doug Heffernan]

(and fixing out of date files with repair_settings.PHP).

Can you please tell us what you mean by this? The aforementioned file doesn't 'fix out of date files', but it checks that all paths/urls are pointing to the right location and provides correction if that is not the case.

Code Select Expand

Fatal error: Uncaught Error: Call to undefined function httpsOn() in /home/DOMAIN/SUBDOMAIN/upgrade.php:285 Stack trace: #0 {main} thrown in /home/DOMAIN/SUBDOMAIN/upgrade.php on line 285

The function mentioned in your error messages is defined in the Subs.php file and by the looks of it said file hasn't been overwritten. What ftp program did you use to overwrite your forum/folder files?

[StarredSkies]

When the host tried to upgrade to 2.0.19, they mentioned this:

2.0.19 was showing you had 'out of date' files.

I ran repair_settings.php and it no longer gives that error.

Looking at my site (after rolling back to 2.0.17), the detailed version check says my sources, details, and language files are all old (2.0.12). So this lines up.


As for what FTP program, I was using CPanel.

Has anyone had any issues going from 2.0.17 to 2.1.4 before? I'm wondering what happens if a clean install of 2.0.17 is done and then try to upgrade from there.

[Doug Heffernan]

As for what FTP program, I was using CPanel.

Try reuploading the files from the large 2.1.4. upgrade package again, but this time use a ftp program for that. It looks like something didn't go right when you overwrote your forum files through the File Manager section of the cPanel.

[StarredSkies]

Alright. I've never used a FTP program before, so I'll look for one and report back. If you have any recommendations, I'm more than open to downloading a specific one.

Will be a second. See ya soon.

[Tyrsson]

Filezilla is free and works. I do not use them often these days so not sure if there are better ones out there.

[MobileCS]

I prefer WinSCP, and it's free as well.

https://winscp.net/

[Kindred]

you can also do what I do when using cpanel

delete the Sources and Themes directories (Save any custom graphics from your default or custom themes that you may want)
delete all php files other than Settings.php in the root
THEN upload/extract all of the 2.1.4 files....

[StarredSkies]

Thank you for the suggestions everyone!

When going from the FTP (WinSCP), it says 'The upgrader found some old or outdated files. Please make certain you uploaded the new versions of all the files included in the package.' (This was not an issue when uploading from CPanel).

I have extracted the upgraded zip file using WinRar while in the subdomain's files.

So, is this an issue with how I am extracting the zip or an overall problem with my files?

I may try Kindred's suggestion in a moment after rolling back.

Edit: trying something else (extracting the upgrade outside of FTP and then moving those files in to the FTP, rather than extracting in FTP)

2nd edit: Trying to do the edit above's idea, it throws out this error: "Warning: Use of undefined constant 'session - assumed ''session' (this will throw an Error in a future version of PHP) in /home/DOMAIN/SUBDOMAIN/Settings.php on line 86

Warning: Use of undefined constant use_only_cookies' - assumed 'use_only_cookies'' (this will throw an Error in a future version of PHP) in /home/DOMAIN/SUBDOMAIN/Settings.php on line 86

Fatal error: Uncaught Error: Call to undefined function httpsOn() in /home/DOMAIN/SUBDOMAIN/upgrade.php:285 Stack trace: #0 {main} thrown in /home/DOMAIN/SUBDOMAIN/upgrade.php on line 285"

Currently using PHP 7.4

Line 86 is: "ini_set('session.use_only_cookies', 1);"
Line 285 is: "if (httpsOn())"

[StarredSkies]

Small update. The host uploaded the upgrade and edited Settings.PHP to match correctly. I will attempt the upgrade now and see if the intimal issues persist.

Edit:
Nope. Still giving me 'Server has not responded for 30 seconds. It may be worth waiting a little longer before trying again.'

Will keep waiting and trying.

Per the host's attempts: "In my testing last night - it did not appear to be doing anything at all while it was 'waiting' beyond waiting. I saw no database queries happening. Not sure where the fault is to be honest."

[Doug Heffernan]

What about your server error log page, are there any errors logged in there recently pertaining to the upgrade?

[StarredSkies]

Nothing is listed. This are the errors from the CPanel (aka none).

[Kindred]

wait wait wait....


you are trying to upgrade a test version of your site?

a copy that you made from your production?
When you made the copy, did you make a database copy and change the references in Settings.php to point to the NEW database and the NEW location of your test site (rather than the production settings?)

[StarredSkies]

Yes. I am testing on a subdomain.

I made a database copy and changed the references in settings.php.

I feel like something is linking because my main site is having troubles logging into the admin panel, editing profiles, and doing a few other things (accessing bookmarks).

Edit: Just used repair_settings.php on the main website's domain and fixed those issues. Even so, it is throwing the same issues as described earlier with line 86 in settings.php.

'Warning: Use of undefined constant 'session - assumed ''session' (this will throw an Error in a future version of PHP) in /home/DOMAIN/public_html/Settings.php on line 86

Warning: Use of undefined constant use_only_cookies' - assumed 'use_only_cookies'' (this will throw an Error in a future version of PHP) in /home/DOMAIN/public_html/Settings.php on line 86

Warning: ini_set(): A session is active. You cannot change the session module's ini settings at this time in /home/DOMAIN/public_html/Settings.php on line 84

Warning: Use of undefined constant 'session - assumed ''session' (this will throw an Error in a future version of PHP) in /home/DOMAIN/public_html/Settings.php on line 86

Warning: Use of undefined constant use_only_cookies' - assumed 'use_only_cookies'' (this will throw an Error in a future version of PHP) in /home/DOMAIN/public_html/Settings.php on line 86'

[Kindred]

when you create a copy install - you need to change the database AND the PATHs AND the URLs both in Settings.php and in the database... 

if you don't then every update that you try to make will be applied to your production install, not your copy install

[StarredSkies]

Where is the information that needs to be changed in the database/paths? And what information needs to be changed? (Any guide/specifics would be helpful)

Just to double check I did it correct. (I repaired settings, copied the database (didn't edit anything), etc)

And does it matter that both databases share the same prefix (smfyv_)?

Edit: Doing a clean install of 2.0.17 on a different subdomain. Encountered this issue and used the fix. Works fine... Going to try upgrading now.

[StarredSkies]

A clean install of 2.0.17 being upgraded to 2.1.14 worked. Hm...

"And does it matter that both databases share the same prefix (smfyv_)?"
Yes. It does. Fool. I switched the database prefix to a new one and edited settings.php to match.

Still nothing.

[Kindred]

prefix doesn't matter, as long as the database itself is different.

The places you have to change are all editable using repair_settings.php -- you will have to run it once to update the database and main path/url settings and then save/exit.  run a second time to update all of the OTHER paths/urls which are stored in the database

[StarredSkies]

Alright. Database is different and the prefix has been changed for my sanity... just in case.

I edited both settings.php and used repair_settings.php. They are both correct.

Out of curiosity, I decided to repeat the process with all of the knowledge above and the error still occurs.



Also tried editing the limit again. Nothing.

If need be, I am open to providing files and trying to have someone replicate the issue.

Question too: could this be a modification issue? I could try another installation and delete all the themes/modifications.