-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in decisions migration from OPS 3.3.0 to 3.4.0 #9533
Labels
Bug:2:Moderate
A bug that is causing problems for a substantial minority of users.
Milestone
Comments
@Vitaliy-1, could you have a look at this (and the attached PR)? Thanks! |
Vitaliy-1
added a commit
to Vitaliy-1/ops
that referenced
this issue
Nov 30, 2023
PR OPS main: pkp/ops#600 |
@touhidurabir, can you take a look at the PR? You worked on it before and know it the best. |
@Vitaliy-1 one comment at https://github.com/pkp/ops/pull/600/files#r1413510912 . |
Vitaliy-1
added a commit
to Vitaliy-1/ops
that referenced
this issue
Dec 5, 2023
Vitaliy-1
added a commit
to Vitaliy-1/ops
that referenced
this issue
Dec 5, 2023
Thanks, @touhidurabir! I've updated the PR but that should go only to stable 3.4.1 |
jonasraoni
added
the
Bug:2:Moderate
A bug that is causing problems for a substantial minority of users.
label
Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently, when upgrading an OPS instance from version 3.3.0 to 3.4.0, we realized that there was a problem migrating editorial decisions.
Searching, we learned that there had been work to centralize the decision constants, described in issue #7725 . Therefore, during the update, a migration is carried out that updates the value of these constants. However, this does not happen in OPS, which keeps the decisions with the old values.
One of our plugins (SciELO Submissions Report) is affected by this problem, generating reports with inconsistent data regarding rejected submissions.
We would be happy to send you a contribution containing a fix for this problem.
The text was updated successfully, but these errors were encountered: