I had something similar that was caused by two issues combining. I had a redirect rule that was kicking in and redirecting to lowercase urls. But, for some reasons, I also had a migration reporting it had run but it hadn't for some reason.
It might be worth just doing the upgrade to 7.6.* first which is the version when the User Management all changed and seeing if you can get past the issue that way?
When you reverted back, did you revert back the database as well? I don't know the install process in detail so I'm not quite sure when things happen but if you didn't revert the database it might already have run the migrations (which I thought ran at start up). It would be worth reverting the database and then checking the migrations table and seeing what migrations it says it's run?
I've checked the database and nothing has changed. No migrations have run and the table still says 7.5.6. So even during all previous attemps the database did not change.
Probably found the issue. The company from which we inherited the project had some custom http modules. After I disabled those the upgrade worked. Now I'm on 7.6.13 and I will continue to upgrade to the latest version. After the upgrade I can enable the http modules again.
We have found exactly the same behavior when upgrading from versions earlier than 7.5.14 to 7.9.* . Our workaround (for now) has been to go to 7.5.14 first then to 7.9.*. I believe, but am not certain, it has to do with the changes to auth/identity/user groups that the upgrade installer does not handle. I have another upgrade (from 4.8.1 :-( ) to complete this week and will keep repro notes in case the pattern holds so I can create an issur on the tracker.
It was an internal module created by the company from which we inherited the project. It's not public available.
The module was a RedirectManager and it did some things Umbraco didn't like. For example add a trailing slash and lower casing. Normally that's not a problem, but during upgrading the installer did not like that.
Installer not working. Upgrading from 7.5.6 to 7.9.2.
Hello,
We inherited a project from another company and the first thing we want to do is upgrade it to the latest version.
The project is upgraded via nuget from 7.5.6 to 7.9.2.
When I visit the website I go to the login screen to start the installer, but the redirect url seems strange:
It seems it wants to go the the authorize page again after login. I tried to login and go to http://project.local/install/. I see the upgrade screen:
When I click continue I get this error:
In the console log I get this:
angular.min.js:106 GET http://project.local/install/api/postperforminstall/ 405 (Method Not Allowed)
This is in the logs:
I've checked several topics:
https://our.umbraco.org/forum/using-umbraco-and-getting-started/89324-ugrading-to-776-invalid-object-name-umbracouser2usergroup
https://our.umbraco.org/forum/using-umbraco-and-getting-started/85475-authorizeupgrade-cant-login#comment-270615
https://our.umbraco.org/forum/getting-started/installing-umbraco/73781-umbraco-nuget-update-728-734-invalid-column-name
https://our.umbraco.org/forum/getting-started/installing-umbraco/52843-Issue-upgrading-from-704-to-712
https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/52792-Upgraded-Umbraco-via-nuget-from-711-to-712-backend-is-blank-yepnope-is-not-defined-
None of the proposed solutions work.
I tried the following:
<Content Include="bin\*Anyone got a suggestion what could be the problem? Thanks!
Jeroen
I had a similar issue still not solved https://our.umbraco.org/forum/using-umbraco-and-getting-started/90342-upgrade-now-cannnot-log-in i have not tried the incongnito login yet
I had something similar that was caused by two issues combining. I had a redirect rule that was kicking in and redirecting to lowercase urls. But, for some reasons, I also had a migration reporting it had run but it hadn't for some reason.
It might be worth just doing the upgrade to 7.6.* first which is the version when the User Management all changed and seeing if you can get past the issue that way?
Hi Nik,
Thanks for the suggestion. Reverted all my changes and now started with an upgrade from 7.5.6 to 7.6.13 to see how that goes.
Jeroen
I tried to upgrade from 7.5.6 to 7.6.13, but I'm getting the same error. I still have no idea how to fix this.
Jeroen
When you reverted back, did you revert back the database as well? I don't know the install process in detail so I'm not quite sure when things happen but if you didn't revert the database it might already have run the migrations (which I thought ran at start up). It would be worth reverting the database and then checking the migrations table and seeing what migrations it says it's run?
I've checked the database and nothing has changed. No migrations have run and the table still says 7.5.6. So even during all previous attemps the database did not change.
Jeroen
Probably found the issue. The company from which we inherited the project had some custom http modules. After I disabled those the upgrade worked. Now I'm on 7.6.13 and I will continue to upgrade to the latest version. After the upgrade I can enable the http modules again.
Jeroen
We have found exactly the same behavior when upgrading from versions earlier than 7.5.14 to 7.9.* . Our workaround (for now) has been to go to 7.5.14 first then to 7.9.*. I believe, but am not certain, it has to do with the changes to auth/identity/user groups that the upgrade installer does not handle. I have another upgrade (from 4.8.1 :-( ) to complete this week and will keep repro notes in case the pattern holds so I can create an issur on the tracker.
-Paul
After I discovered that the issue was related to a 3rd party http module I started from scratch.
I disabled the http module and did a direct upgrade from 7.5.6 to 7.9.2 without any issues.
Jeroen
Which 3rd party http module was causing the issue for you (So others would know if they are similarly affected)? Thanks!
Hi Frank,
It was an internal module created by the company from which we inherited the project. It's not public available.
The module was a RedirectManager and it did some things Umbraco didn't like. For example add a trailing slash and lower casing. Normally that's not a problem, but during upgrading the installer did not like that.
Jeroen
Commenting out Trailing slash rule during installation worked for me.
is working on a reply...