8000 pkp/pkp-lib#13708 Remove the unversioned Static Pages migration that moved pages on every upgrade by mesutk · Pull Request #6018 · pkp/ojs · GitHub
[go: up one dir, main page]

Skip to content

pkp/pkp-lib#13708 Remove the unversioned Static Pages migr 8000 ation that moved pages on every upgrade - #6018

Open
mesutk wants to merge 1 commit into
pkp:stable-3_5_0from
mesutk:i13708-stable-3_5_0
Open

mesutk wants to merge 1 commit into
pkp:stable-3_5_0from
mesutk:i13708-stable-3_5_0

Conversation

@mesutk
@mesutk mesutk commented Nov 4, 2026 •
Copy link
Copy Markdown

Fixes pkp/pkp-lib#13708

migrateStaticPagesToNavigationMenuItems sits outside any <upgrade> block in dbscripts/xml/upgrade.xml, so it runs on every upgrade. Each time, it moves every page out of the Static Pages plugin into a Custom Page navigation menu item and deletes it from static_pages. That was useful once, for the switch to navigation menus in 3.1. Today Static Pages is still bundled and in use, and anything older than 3.3 is already aborted earlier in this file, so the only pages this step still moves are ones people made on purpose.

This removes the call. The now unused Upgrade::migrateStaticPagesToNavigationMenuItems() and NavigationMenuItemDAO::portStaticPage() stay in place here to keep the change small; on main they're removed in #6019 and pkp/pkp-lib#13710.

Tested by upgrading an OJS journal from 3.5.0-5 to 3.5.0-6 with this line removed: static pages and menus were unchanged and the rest of the upgrade ran as normal. Upgrading OMP 3.5.0-5 to 3.5.0-6 with the line in place moved all 30 of the press's static pages.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[OJS/OMP 3.5] | Upgrade - upgrade.xml, Static Pages are moved to Custom Pages on every upgrade

1 participant

0