Updating Avada from Older Versions
Last Update: May 16, 2023
Why you should update regularly
A major reason to keep Avada and your plugins up-to-date is for security purposes. Keeping your site updated ensures that you have the latest security fixes, and that your site is following the latest security best practices available. For detailed information on security in WordPress, please see the Hardening WordPress article.
If you’ve fallen behind on updates, or you’re taking over a new project that hasn’t been updated in a while, this post will guide you in updating from older versions of Avada up to the latest.
Recommended Update Path:
With each new Avada update comes a set of new options, features and code improvements. Click on the version path that matches your current Avada version for detailed instructions
Updating From Avada 3.9 And Older
Regardless of what version of Avada you have currently, if it’s before Avada 3.9, then 3.9.4 should be the first stage in the update. If you haven’t checked the Pre Update Tips section from above yet, click here for that important information.
If you’re updating from an Avada version before Avada 3.8 and you have custom CSS, you’ll need to check your custom CSS after the update, due to a CSS refactor in Avada 3.8. Because of the refactor, your custom CSS classes may also need updating, so they match the new classes used in Avada.
For information on custom CSS in Avada, please read our How To Make Custom CSS Changes doc.
If you have no customizations or custom CSS in your theme, then the update to 3.9.4 should be routine. For standard update information, please see our guide here.
After the update has completed, then clear your cache completely and check your site over to see if everything is working well. Since this is still an older version of Avada, it’s recommended that you have your plugins disabled, aside from the Avada Core plugin, while testing your site. This is to ensure any issues you see aren’t related to a plugin conflict. The primary goal here is to just ensure that the theme styling is how it should be, then on to the next update.
Updating From Avada 3.9.X
When updating from Avada 3.9.X, your next stage in the update chain will be 4.0.3. If you’re not at 3.9.X yet, follow the steps in the section above, before proceeding. If you haven’t checked the Pre Update Tips section from above yet, click here for that important information.
In Avada 4.0.X, the most notable change was the migration from the old Avada Global Options to the new Avada Global Options.
To be sure the Global Options migration completes correctly, you’ll want to double check your Avada System Status page and increase any limits that are showing a red notice (with the exception of max_input_vars as that will have no effect on the migration). Please see here for information on increasing your server limits and here for information on server requirements in Avada.
As an extra precaution, it’s recommended that you disable all non-Avada plugins (with the exception of WPML if in use), while the migration is being processed. This will ensure your Global Options migration isn’t hindered by a plugin conflict.
If you get get trapped in the migration (e.g. The migration steps are endlessly repeating, or are frozen.), then you can correct this with FTP access. If you didn’t disable your plugins, then you may have a plugin conflict. You can fix this by changing the name of the wp-content/plugins directory to something else temporarily. (e.g. wp-content/plugins-dis) That will disable all the plugins and allow the migration to complete.
Updating From Avada 4.0.X
If your current Avada version is 4.0.X, then your next stage in the update will be Avada 5.9.1. This will include the conversion of your shortcodes from the old Avada page builder to the new Avada Builder which was introduced in Avada 5.0.
If you’re not at 4.0.X yet, please reference the appropriate section above for your current Avada version, before proceeding. If you haven’t checked the Pre Update Tips section from above yet, click here for that important information.
Since the Avada Builder uses different shortcodes, any shortcodes generated by the Avada page builder prior to Avada 5.0 will not render elements and will only appear as plain text. There’s an automated conversion process which will occur to update your content to the new shortcode syntax.
Areas that are automatically converted by Avada include: pages, blog posts, portfolios, WooCommerce product content and excerpts, widgets, global options, Avada Sliders, Revolution Sliders and LayerSliders.
If after the update, your site is showing all shortcodes on the front end of the website, the conversion may not have completed correctly. Although it looks like a serious problem, it’s normally just due to low server limits causing the update process to be truncated. To fix this, you can manually trigger the shortcode conversion again at the top of the System Status page. If that doesn’t correct the issue, double check that the Avada Builder plugin is installed and activated.
Updating From Avada 5.9.1
If your current Avada version is 5.9.1, then your next stage in the update will be the latest version of Avada. The current latest version is Avada 7.10.1, which includes a new registration method. For more details about the registration, please see the Changes To the Avada Registration Method.
If you haven’t checked the Pre Update Tips section from above yet, click here for that important information.
If you have trouble with the update and you need additional help, please submit a support ticket to our support center and we’ll check into it ASAP. Please fill out all the requested fields in the ticket submission form to avoid delays.