Project

General

Profile

Actions

Defect #37118

closed

NoMethodError in account CRUD operations.

Added by Mujassim Jamal almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Accounts / authentication
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Hi, I am getting NoMEthodError while creating or adding new user including authentication and accounts CRUD operation.

Everything is working fine except the accounts/authentication operation.

Does anyone know how to solve this error?


Files

Redmine-500-error.png (21 KB) Redmine-500-error.png Mujassim Jamal, 2022-05-14 10:07
logs.png (98.4 KB) logs.png Mujassim Jamal, 2022-05-14 10:07
redmine-information.png (61.4 KB) redmine-information.png Mujassim Jamal, 2022-05-14 10:07
Actions #1

Updated by Pavel Rosický almost 2 years ago

did you migrate to redmine 5 already? you can't switch back to redmine 4 without restoring the database schema

1/ use a backup before the redmine 5 upgrade (you'll lose all data since then)
2/ upgrade to redmine 5, revert all migrations back to your desired version
3/ add missing columns manually, but this could cause inconsistencies / failures in the future because the migrations_schema won't match the real DB state.

Actions #2

Updated by Mujassim Jamal almost 2 years ago

Pavel Rosický wrote:

did you migrate to redmine 5 already? you can't switch back to redmine 4 without restoring the database schema

1/ use a backup before the redmine 5 upgrade (you'll lose all data since then)
2/ upgrade to redmine 5, revert all migrations back to your desired version
3/ add missing columns manually, but this could cause inconsistencies / failures in the future because the migrations_schema won't match the real DB state.

Yes, i did migrate to version 5 once then i switch back to the previous version & got this error.

As you specified in second point, how can i revert all migrations back to the previous version?

Also, Redmine is running on docker instance so is there any other alternative solution there?

Actions #3

Updated by Mujassim Jamal almost 2 years ago

  • Status changed from New to Resolved
Actions #4

Updated by Holger Just almost 2 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF