Database structure mismatch over notification entity for new OJS 3.4 installations #10070
Labels
Bug:1:Low
A bug that does not have a severe consequence or affects a small number of users.
Milestone
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
The text was updated successfully, but these errors were encountered: