Jump to content

Curious about consistency end of upgrade/update.


Go to solution Solved by Ryan Ashbrook,

Recommended Posts

Posted
2 minutes ago, Nathan Explosion said:

One is a patch being applied, which is done all within the ACP (the one you have pictured)

The other is a full upgrade which takes you out of the ACP, and when completed presents you with the choice to go to the site, or to the ACP.

4.6.11 ended like the screenshot above.

  • Solution
Posted
1 minute ago, Nathan Explosion said:

One is a patch being applied, which is done all within the ACP (the one you have pictured)

The other is a full upgrade which takes you out of the ACP, and when completed presents you with the choice to go to the site, or to the ACP.

Actually, there's quite a bit more to it than that. 🙂

There are some specific circumstances where even if you go from, for example, 1.2.3 to 1.2.4, then it can all be done within the AdminCP. If there are more significant changes, however, then it will send you to the full upgrader.

Posted (edited)
3 minutes ago, Adriano Faria said:

4.6.11 ended like the screenshot above.

Can't say I noticed that, to be honest.

1 minute ago, Ryan Ashbrook said:

If there are more significant changes

Which would normally be expected in an upgrade, if there are theme updates/database changes/language changes or so forth.

Edited by Nathan Explosion
Posted
1 hour ago, Nathan Explosion said:

Which would normally be expected in an upgrade, if there are theme updates/database changes/language changes or so forth.

The AdminCP upgrader can actually handle those. For instance, if you were going from 4.6.0 to 4.6.1, then it would not likely kick you to the full upgrader because the only changes between those versions were code changes, theme changes, and JavaScript changes.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...