Version 1.17 of the oik base plugin includes logic to relocate child plugins when activated, causing them to become standalone plugins. These standalone plugins are supported from the oik-plugins server. Administrators of WordPress Multi Site implementations should take special care when upgrading to oik version 1.17. The recommended technique for upgrading is summarised below.
oik v1.17 WPMS update guide
As the Network Administrator of the Multi Site implementation
- Perform a backup; recommended when performing any upgrade
- Put the site into Maintenance Mode using an appropriate plugin
- Update the oik base plugin
- Network Activate the oik base plugin
- For each of the child plugins – oik-bbpress, oik-bob-bing-wide, oik-bp-signup-email, oik-bwtrace, oik-email-signature, oik-fields, oik-header, oik-sc-help and oik-sidebar
- If not already activated then Network Activate the child plugin. This will cause it to be relocated to become a standalone plugin.
- If not required as Network Activated then Network Deactivate the plugin.
- If not required at all then Delete the plugin. Remember: You can download the latest standalone version from oik-plugins if you find you did need it after all.
- Visit each of the Site’s Dashboard > Plugins > Installed plugins
- Take the site out of Maintenance mode
- Perform another backup
Do I need to perform Update Network?
No, not if you have only updated the oik base plugin.
Do I need to update oik options?
No, unless you want to make changes.
What happens if a child plugin was already activated in a site?
When visiting the Site’s Dashboard, you may see a message indicating that the plugin is missing so has been deactivated. If so, you can reactivate the plugin.
Tell me more about plugin relocation
I have another problem not listed
Please write and tell us about the problem. Contact oik