Installing updates just involves replacing the old plugin files with the new ones. It’s always a good idea to back everything up before you upgrade (plugin directory & database), especially if you have made any changes to UberMenu’s files, as the upgrade will overwrite all files.
If you are running UberMenu version 3.2.4 or later, you can now use Automatic Updates. Remember, it’s always a good idea to back up your site before running any type of update.
UberMenu settings set through the control panel will all remain intact.
As of UberMenu 3.1.1, update alerts are built in to UberMenu. To receive these alerts, open your UberMenu Control Panel, click the Updates tab, and then enter your Envato data. (Please note these are update alerts, not automatic updates)
Please note that this data will be sent to the update server for registration and validation – this includes your CodeCanyon username, purchase code, site URL, and UberMenu plugin version.
How to get updates
To download the updated plugin zip, go to your CodeCanyon Downloads page and re-download the file. This will always give you the latest version of the plugin.
Now is a great time to rate the plugin 5 stars if you haven’t already. Giving 5 star ratings helps us keep pushing out feature and maintenance release updates. Thanks so much!
Automatic updates are
currently in beta now out of beta as of version 3.2.4. If you are currently running UberMenu 3.2.1 – 3.2.3, and would like to beta test automatic updates, please follow the instructions here: Automatic Updates (Beta).
If you are running a version earlier than 3.2.1, please follow the instructions below to update manually.
- It is always a good idea to back up your plugin before making any changes
- Open your FTP program and FTP into your site and navigate to the
- Download the
ubermenufolder and save it as a backup
- If you have edited any files, especially the
custom.jsfiles, you should back up these files.
If you want an auto-backup plugin, you might want to check out WordPress Backup to Dropbox
Migration from UberMenu 2 to UberMenu 3
Version 3 is a MAJOR upgrade. Please be sure to test this on a test server before deploying to your live site, and always take a backup before making any changes to a live site.
If you are upgrading from UberMenu 2 to UberMenu 3, please follow the UberMenu Migration Instructions after installing the new version via the instructions below, in order to migrate your settings. Please read through the migration instructions before beginning the upgrade process.
If you are using any UberMenu Extensions, you will also need to update them to their 3.0 versions for compatibility with UberMenu 3
Standard Update Instructions
- Download the new version of the plugin from CodeCanyon (the latest version can always be found on your CodeCanyon Downloads page.
- In your browser, log into the WordPress control panel.
- Navigate to Plugins
- Deactivate UberMenu (optional, but generally a good idea, especially if you are deleting the old version in step 6)
- Switch to your FTP program, FTP into your site and navigate to the
- After backing up (especially
custom.cssif you are using one), delete UberMenu (the entire
ubermenufolder). Strictly speaking, this is optional, but makes the upload process more straightforward. You can also overwrite the old files if you prefer. (Please check for version-specific upgrade instructions; sometimes a deletion is strongly recommended)
- On your desktop, decompress the zip file you downloaded from CodeCanyon
- Open the unzipped folder, which will contain a new
- FTP the new
ubermenufolder into the
wp-content/pluginsdirectory on your server.
- If you saved an edited copy of your
custom.cssfile as a custom preset (or
custom.js), upload it to
- Ensure that your permissions are set properly on the
plugins/ubermenudirectory. If your server can’t read the files, you might run into errors. This can happen depending on how your FTP account is set up.
- Switch back to your browser and go back to the Plugins panel
- Reactivate UberMenu by clicking Activate
Note: If you are running a local server, just copy the files rather than FTPing