Skip to content
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

Database structure mismatch over notification entity for new OJS 3.4 installations #10070

Closed
jonasraoni opened this issue Jun 17, 2024 · 1 comment · Fixed by #10068, pkp/ojs#4321, pkp/ops#713, pkp/omp#1602 or pkp/omp#1603
Assignees
Labels
Bug:1:Low A bug that does not have a severe consequence or affects a small number of users.
Milestone

Comments

@jonasraoni
Copy link
Contributor

Describe the bug
This is a follow-up of #8592, where the migration to make the field notification_subscription_settings.context_id nullable was partially done.

A migration to set the null flag was added, but the migration that creates the table wasn't synchronized, the outcome is that new installations will be missing the null flag, while upgraded installations will have it.

What application are you using?
OJS 3.4

@jonasraoni jonasraoni added the Bug:1:Low A bug that does not have a severe consequence or affects a small number of users. label Jun 17, 2024
@jonasraoni jonasraoni added this to the 3.4.0-6 milestone Jun 17, 2024
@jonasraoni jonasraoni self-assigned this Jun 17, 2024
@jonasraoni
Copy link
Contributor Author

@touhidurabir, I've moved the PRs to this issue, feel free to review, I'll just update the commit message to use the right ticket number later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment