Jump to content

Infinite loop of screens when trying to upgrade to 4.7.6


Go to solution Solved by Jim M,

Recommended Posts

12 minutes ago, Jim M said:

Are you receiving any errors in your browsers console when this happens? Can click F12 > Console to see the browser console. 

When I click 'Upgrade Now' in the banner at the top of the ACP the following shows up in the Console. As I click through Step 1, still looping through, nothing else shows up:

JQMIGRATE: Migrate is installed with logging active, version 3.3.0 root_library.js:10:16
JQMIGRATE: jQuery.fn.bind() is deprecated root_library.js:12:302
console.trace() root_library.js:12:373
    migrateWarn https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:12
    bind https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:49
    bind https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:56
    initCore https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:56
    init https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:56
    <anonymous> https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:56
    <anonymous> https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:56
JQMIGRATE: JQMIGRATE: jQuery.cssProps is deprecated root_library.js:12:302
console.trace() root_library.js:12:373
    migrateWarn https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:12
    set https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:32
    <anonymous> https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:60
    <anonymous> https://www.bzpower.com/uploads/javascript_global/root_library.js?v=f07b1c28e31673560696:60
This is a browser feature intended for developers. Do not paste any code here given to you by someone else. It may compromise your account or have other negative side effects. root_library.js:71:364
Some cookies are misusing the recommended “SameSite“ attribute 4
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.google-analytics.com/j/collect?v=1&_v=j98&a=2136967474&t=pageview&_s=1&dl=https%3A%2F%2Fwww.bzpower.com%2Fadmin%2F%3Fapp%3Dcore%26module%3Dsystem%26controller%3Dupgrade&ul=en-us&de=UTF-8&dt=Upgrade%20Invision%20Community&sd=24-bit&sr=3440x1440&vp=1449x767&je=0&_u=AACAAEABAAAAACAAI~&jid=&gjid=&cid=1952441680.1638105045&tid=UA-33219329-1&_gid=1794900386.1673560687&_slc=1&z=614939575 analytics.js:43:31

 

Link to comment
Share on other sites

8 minutes ago, dutchsnowden said:

Gosh no, not that, I guess I will wait for the next update. Thank you so much for the link.

The issue will still be there even for the next update since it's in your current version. If you're unable to get past that step, no matter how many versions you skip/wait it won't change. Because the new files aren't downloaded at that point yet.

If you're uncomfortable doing the manual upgrade yourself maybe you can get someone else to do it for you? Manual upgrades are easy enough as long as you know what you're doing. I do them often myself.

Edited by teraßyte
Link to comment
Share on other sites

It means the underlying issue that allowed this situation to happen will be fixed. If something is already preventing you from using the auto updater with the current version, nothing in future releases will fix the CURRENT updater other than downloading the files from your client area and uploading them to your site (aka “a manual update”).

Link to comment
Share on other sites

1 hour ago, dutchsnowden said:

Sorry? What underlying issues? The updater should be prepared for all cases, as I updated and took care of every single update in time and with much care. 

As for manual update, is not hard, I know, but I still getting PTSD from 3.x upgrade a year ago. I don't want anymore.

This would be a bug in the upgrader which is present in the version on your server. The only way to get past that would be to manually upgrade.

This minor upgrade will be significantly more simple than the version 3 upgrade which was not only a significant, major software upgrade for you but a large server upgrade to run version 4. 

Link to comment
Share on other sites

19 minutes ago, Jim M said:

This would be a bug in the upgrader which is present in the version on your server. The only way to get past that would be to manually upgrade.

This minor upgrade will be significantly more simple than the version 3 upgrade which was not only a significant, major software upgrade for you but a large server upgrade to run version 4. 

My concern would be the database table changes that are apparently required to go from 4.7.5 to 4.7.6, at least based on the malfunctioning auto-updater. Is there a way to know what changes we have to make in order for the upgrade to complete successfully?

Link to comment
Share on other sites

11 minutes ago, Black Six said:

My concern would be the database table changes that are apparently required to go from 4.7.5 to 4.7.6, at least based on the malfunctioning auto-updater. Is there a way to know what changes we have to make in order for the upgrade to complete successfully?

The upgrader will handle that. You upload the files then run the upgrader at /admin/upgrade 

Link to comment
Share on other sites

59 minutes ago, Jim M said:

This minor upgrade will be significantly more simple than the version 3 upgrade which was not only a significant, major software upgrade for you but a large server upgrade to run version 4. 

Not even sure what it was, I recall it took 3 days out of my life and not sure what happened. I installed times and times again then again, and nothing was working.

Link to comment
Share on other sites

30 minutes ago, dutchsnowden said:

Not even sure what it was, I recall it took 3 days out of my life and not sure what happened. I installed times and times again then again, and nothing was working.

This is like comparing apples to oranges, upgrading from version 3.x to 4 and 47.5 to 4.7.6. Manually upgrading is exactly the same as the auto upgrader but you’re moving the files instead of the software. Upgrading from 3.x is a huge upgrade, this is a minor upgrade so not as many changes going on. 

Link to comment
Share on other sites

Think of it this way… the further behind you are on versions, the harder it is to upgrade. 

Moving between minor point versions are MUCH less likely to run into issues. But the further behind you are, the more likely it is you’re going to feel pain. Upgrading from 3.X to 4.X is like 100 upgrades rolled into one. It WILL be painful. However just one will be fine in 99% of cases. 

Link to comment
Share on other sites

8 hours ago, Randy Calvert said:

Moving between minor point versions are MUCH less likely to run into issues. But the further behind you are, the more likely it is you’re going to feel pain. Upgrading from 3.X to 4.X is like 100 upgrades rolled into one. It WILL be painful. However just one will be fine in 99% of cases. 

Confused Always Sunny GIF by It's Always Sunny in Philadelphia

Link to comment
Share on other sites

1 hour ago, dutchsnowden said:

Manual SQL querries is my middle name.

 

Thats a unique middle name!

1 hour ago, dutchsnowden said:

@Stuart Silvester I can confirm it is working now, thank you so much. I stopped it so I can choose a better hour to do this for online service availability but will confirm once again when I did it and completed. Thanks again!

Glad to hear you are now upgraded

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Upcoming Events

    No upcoming events found
×
×
  • Create New...