[OJS3.x] Problems upgrading from OJS 3.1 to OJS 3.2 - unable to save administration settings

Hello all, @NateWr, @asmecher, @Dimitris_Efstathiou,

After a lot of testing and analysis, we came to the following situation, reported over a year ago here:

  • During upgrade, administration menu upgrade is skipped because it exists;
  • After “successful” upgrade from OJS 3.1 to OJS 3.2 administration interface SAVE button doesn’t work because it cannot find the reference to the correct address, as it came from a previous version;
  • Links in this “menu” are Javascript and added to the database, but are not updated during upgrade.

This may be the reason why we are unable to save Administration settings when upgrading to OJS 3.2. I didn’t want to bump the old post.

[UPDATE AUGUST 18 @ 10H46 GMT-3]
From what we found, this is the only possible explanation for our issues with OJS 3.2 upgrade. Because of the impossibility to save administration settings, we have to remove our custom theme first from OJS 3.1, before upgrading to OJS 3.2, otherwise, we are unable to apply default theme, as our custom theme is for OJS 3.1 and it becomes unavailable after the upgrade.

From the discussion on post Error with my custom theme…, it seems not to be an issue, but, who knows…

Here’s our log:

[code: Installer Installer::installDefaultNavigationMenus]
WARNING: The NavigationMenu (ContextId: 1, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 1, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 2, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 2, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 5, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 5, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 9, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 9, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 3, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 3, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 4, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 4, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 8, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 8, Title: Primary Navigation Menu, Area: primary) will be skipped because the specified area has already a NavigationMenu attached.
WARNING: The NavigationMenu (ContextId: 0, Title: User Navigation Menu, Area: user) will be skipped because the specified area has already a NavigationMenu attached.

I think those warning messages are ok. The upgrade script will automatically assign a navigation menu to a nav area if none is assigned. In your case, it looks like the upgrade script is behaving correctly by skipping that step where the nav menus are already assigned.

Either way, the navigation menu stuff shouldn’t be effecting your admin settings.