installation-maintenance 归档

Updating to Avada 6.0 – What To Expect

While the update to Avada 6.0 is a massive one in terms of feature set, behind the scenes, it』s pretty much just a regular update. There are no conversions required, and it is a standard update with no special steps.
As usual, you should, of course, have a full backup of your site before updating, and if you are updating from older versions, please read the Updating Avada From Older Versions document.
Do not attempt to update directly to Avada Live if you are on any version prior to 5.0. For versions older than this you will have to perform an incremental upgrade.
We recommend you keep your site fully up to date with every version. This will ensure there are no security problems from unpatched issues, and always allow a smooth upgrade process.

General Update Information

With each new Avada update comes a set of new options, features, and code improvements. Our team always ensures we make everyone aware of any important items that will show in the new update. This post outlines several items that should be taken into account anytime you update your theme. Being aware of these items can drastically reduce avoidable issues when updating Avada or any theme.
General Update Information1. It Is Always Recommended To Backup Your Current Setup
It』s always a good idea to make sure that you have a current backup of your web site, including your wp-content folder, your wp-config.php file, and your .htaccess file in your WordPress installation folder, and a copy of your WordPress database. You can use these to revert back to your original site if something unforeseen happens during the update process. If you are not familiar with how to do this yourself, there are several plugins available that completely automate that process for you, such as: UpDraft Plus and WordPress Backup Buddy
If you are using the Revolution Slider and have added custom css, please make a backup of the styles because those will be removed when you update. You can also backup your Avada Theme Options by generating an export file from the Import / Export tab in Avada > Theme Options > Import / Export. Read our Backing Up Your Site & Theme Options document for more information on that process.
2. Do Not Keep Older Copies of The Theme In WP Theme Folder
You should completely remove all previous Avada theme folders before adding the new updated theme folder, or you could end up with WP path issues, etc.

3. Do Not Rename The Theme Folder
If you rename your theme folder when you update, then the path is no longer valid. WordPress stores menus and widget settings and some other settings by folder path. You need to rename your theme folder back to what it was before, and your settings, menus, widgets will be restored. Make a copy of your current theme folder before you upload the new theme.

4. Reset Browser Cache, Server Cache And Plugin Cache
It is always recommended to reset your browser, plugin, and server cache when you update. Visual issues may occur after an update. This is something easily avoided by clearing your cache after all updates. Each browser allows you to remove cookies, history and other data. If your theme or Avada Core version is not updated after uploading the new files, it is due to a server-side caching system. Some hosting providers have server-side cache systems installed to optimize the speed of content delivery, please clear any server-side cache or ask your host to do it. This is also true for Google Pagespeed setups or Cloudflare setups.
Read this document for more details on clearing various forms of cache.

5. Required & Recommended Plugins Must Be Updated
When you update the theme, you will see a notification message in your admin telling you the required and recommended plugins need to be updated. Follow the onscreen prompts to install the plugin updates. The Avada Core and Avada Builder plugins are the only required plugins. These have to be installed and activated for the theme to work correctly. Make sure you are always using the most recent version of the Avada Core and Avada Builder plugins available for your theme version. If the required Avada Core and Avada Builder plugins are not active or not running the latest available versions, you will see a notice at the top of your WordPress admin pages. If you dismiss the prompt or do not see it, then from your WP Admin, navigate to Avada > Plugins & Add-ons and activate/update the plugins as needed. Every time you update the theme, the Avada Core and Avada Builder will also need updated.
6. Compatibility With WordPress 5.0WordPress version 5.0 was released on December 6th, adding Gutenberg to the WordPress core. The release was delayed several times and we and we have prepared a comprehensive article, WordPress 5.0, Avada, & You. All That You Need To Know, to keep you abreast of progress.
Update Information

System Status

The System Status page contains a collection of relevant data that will help you debug your website accurately and more efficiently. In this tab, you can also generate a System Report, which you can include in your support tickets to help our support team find solutions for any problems you may have much faster.
This page is divided into seven sections; Avada Version History, Avada Conversion Controls, WordPress Environment, Server Environment, Updates Server Status, Avada Forms, and the Active Plugins section. The System Status page is located at Avada > Status in your WordPress Admin Sidebar, or from the Avada Dashboard, head to Maintenance > Status. Continue reading below for more information on each section, and watch the video for a visuial overview.
Avada Version History & Conversion ControlsThe Avada Version History & Conversion Controls sections show the current theme version and your previous versions, as well as several utility buttons that relate to various version』s migrations and conversions. The content you see in this section will vary depending on which versions you』ve used. For more information on each item which may be displayed in this section, view the list below.
Current Version: – This section will display the version number of the currently active Avada theme.Previous Versions: – This section will display the Avada update history for this site up-to the last three updates.Avada 4.0 Migration: – If you started using Avada on a version pre-Avada 4.0, then you will see a section which relates to the Theme Options migration to the Avada 4+ Theme Options framework. Click here for more details on the migration.Avada 5.0 Conversion: The Avada 5 update ushered in a new Fusion Builder Plugin which was completely rebuilt and refactored from the previous page builder included with Avada. The Fusion Builder plugin used a new shortcode syntax. Because of this, it required a conversion from the old builder』s shortcode syntax to the new Fusion Page Builder』s syntax. If you had an Avada version pre-Avada 5.0 installed, your content would have been converted upon update and the below buttons would have been listed on the System Status page for your site.Run Conversion: – This button can be used to manually start the shortcode conversion process on your site. Click here for more details on this.Revert Conversion: – This button will revert your page content to how it was before the update and shortcode conversion took place. Click here for more details on this.Remove Backups: – This button will remove the Fusion Builder backups that were created when you updated your site. Doing this will mean you cannot automatically revert your site and the 「Revert Conversion」 button will also be removed. Click here for more details on this.
Avada 6.1.1 Conversion: – Run Conversion Button – This button will rerun the Theme Options Conversion for version 6.1.1 manually.

Avada 7.4.1 Conversion: – Run Conversion Button – This button will rerun the Global Options Conversion for version 7.4.1 manually.
IMPORTANT NOTE: The contents on this section will vary based on the version you have started from and version you are currently on. See examples below.If you started on version 3.9.4 or lower, and are on the latest version 5.4.2, then, you should see 4.0 conversion button and 5.0 conversion button, as well as the revert Fusion Builder conversion button.If you started on version 4.0, and now on the latest version 5.4.2, then, you should only see 5.0 conversion button, as well as the revert Fusion Builder conversion button.
If you started on version 5.0 or higher, you will only see the Avada 6.1.1 Conversion Controls.

If you started on version 6.0 or higher, you will only see the Avada 7.4.1 Conversion Controls.
WordPress EnvironmentThis section displays all the relevant data that has to do with your WordPress environment.
Home URL – This item displays the URL of your site』s homepage.Site URL – This item displays the root URL of your site.WP Content Path – This item displays the system path to this WordPress install』s wp-content directory.WP Path – This displays the system path to the WordPress install』s root directory.WP Version – This item displays the version of WordPress installed on your site.WP Multisite – This item displays whether or not you have WordPress Multisite enabled.PHP Memory Limit – This item displays the maximum amount of memory (RAM) that your site can use at one time.WP Debug Mode – This item displays whether or not Debug Mode for WordPress is enabled.Language – This item displays the current language used by WordPress.Server EnvironmentThis section displays all the relevant data that has to do with your server environment.
Server Info – This item displays information about the web sever that is currently hosting your site.PHP Version – This item displays the version of PHP installed on your hosting server.PHP Post Max Size – This item displays the largest size that your post data can reach. That includes all post content (images, text, etc.)PHP Time Limit – This item displays the amount of time (in seconds) that your site will spend on a single operation before timing out.PHP Max Input Vars – This item displays the maximum number of variables your server can use for a single function to avoid overloads.SUHOSIN Installed – This item displays whether or not SUHOSIN is installed.ZipArchive – This shows whether or not ZipArchive is installed on yours server. This is needed for demo imports.MySQL Version – This item displays the version of MySQL installed on your hosting server.Max Upload Size – This item displays the largest file size that can be uploaded to your WordPress installation.DOM Document – This item displays whether or not DOM Document is installed. This resource is needed for the Fusion Builder to function correctly.WP Remote Get – This item shows whether or not wp_remote_get() is functioning correctly. This is used by Avada for communication with different APIs. (eg. Google, Twitter, Facebook)WP Remote Post – This item shows whether or not wp_remote_post() is functioning correctly. This is used by Avada for communication with different APIs. (eg. Google, Twitter, Facebook) GD Library – This item displays if the GD Library is installed and what the active version is.,Red and Green ValuesIn the System Status tab, some values may appear as green or red. If a value appears as green, this means that the value satisfies the minimum requirements needed to run the theme. If a value appears as red, this means that the value is below the minimum requirements and needs to be adjusted. Please click the button below to read about how to increase these limits.
How To Adjust System Status Limits,Avada Update Server StatusThe top part of this next section, as seen in the screenshot below, allows you to check the Avada Server Status, and will display advanced server response output for remote get requests. If you get a green message saying 「Tested API is working properly.」, means you should be good with the server and you should be able to update Avada, supplied plugins, import prebuilt websites, or apply patches with no problem.
If you get a red message, means there is something wrong and the messages and response codes can vary based on your setup. A short error log will be displayed providing you with the needed details which corresponds to the response codes.
Avada FormsThe bottom part of the section, as you can also see in the screenshot above, offers a button to Re-create Avada Forms Database Tables. These database tables get auto-created on update to 7.1, but if for some reason, they are not, users would see PHP notices, and Avada Forms would not work as expected. This buttons tries to create the tables again in such a case. If you continue to have troubles with this, consult your host, or submit a support ticket.,Active PluginsThis section displays all your active plugins. The Avada Core, Avada Builder, LayerSlider, Slider Revolution, Advanced Custom Fields PRO, Avada Custom Branding, and Convert Plus are plugins included with the theme. Please ensure that the Avada Core and Avada Builder plugins are always active and up-to-date.
Avada Core – This plugin is created by ThemeFusion, and is a required plugin. Please make sure it』s always active and up-to-date.Avada Builder – This plugin is created by ThemeFusion, and is a required plugin. Please make sure it』s always active and up-to-date.
LayerSlider WP – This plugin is created by Kreatura Media, and is an included plugin.

Slider Revolution – This plugin is created by ThemePunch, and is an included plugin.

Advanced Custom Fields PRO – This plugin is created by Elliot Condon, and is an included plugin.

Avada Custom Branding – This plugin is created by ThemeFusion, and is an included plugin.

Convert Plus – This plugin is created by Brainstorm Force, and is an included plugin.

How To Adjust System Status Limits

On the Avada > System Status page, you』ll find some WordPress and Server Environment limits to check, to ensure your site runs smoothly. Any values in red may need increasing. Below you』ll find the most common limits that users encounter issues with. Continue reading below to learn more about what these values are, why they need to be adjusted and how you can go about adjusting them.
IMPORTANT NOTE: Please know that each hosting service is different, and the methods mentioned below may, or may not, work for you. Before trying these methods to increase your system status limits, it』s always best to contact your host first and ask them if they can make these adjustments for you.,OverviewWP Memory Limit
PHP Time Limit
PHP Max Input Vars,WP Memory LimitWhat Is The WP Memory Limit?The WP Memory Limit is the maximum amount of memory (RAM) that your site can use at one time. When you reach your Memory Limit, you』ll encounter a fatal error. Several things consume memory, such as WordPress itself, the theme you』re using, and the plugins installed on your site. Basically, the more content and features you add to your site, the higher your memory limit has to be.
Why Do I Need To Increase My WP Memory Limit?There are a number of factors that may affect how much memory your website will need such as content, themes, plugins, etc. The default memory limit for WordPress is 32MB. If you』re only running a small site with basic functions, this default value is more than enough. However, once you start encountering 『Fatal Error: Memory Size Exhausted…, it may be time to adjust your memory limit.
How To Increase The WP Memory LimitTo increase your memory limit, you』ll need to access and modify certain files such as the php.ini, wp-config.php, and .htaccess files. Most hosts won』t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.
For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other methods. For standard users, we encourage you to try Method 2 and Method 3 instead.
Method 1: Change Your PHP Memory Limit in php.ini FileIMPORTANT NOTE: Many shared hosts prohibit you from having direct access to the PHP.ini file. Only do this method if you have direct access to your PHP.ini file or if you』re on your local host or own server setup. Please note that this won』t change the red WP Memory Limit value reflected in your System Status tab since this method adjusts your PHP memory limit.Step 1 – Locate your PHP.ini file. If you can』t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.
Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):
Copy to Clipboardmemory_limit = xxM; 1memory_limit = xxM;Then change xxM to your desired limit. For example, 256M.
Step 3 – If you created your own PHP.ini file, then add the same code inside it:
Copy to Clipboardmemory_limit = 256M;xxxxxxxxxx1 1memory_limit = 256M;Simply change the value to the recommended value. For example, 256M.
Step 4 – Save your changes, and reboot your local host or server.
Method 2: Change Your WordPress Memory Limit in WP-config.php FileIMPORTANT NOTE: This is the value that you see displayed on the WP Memory Limit status on the System Status page. Changing this value to the recommended value (256M) will turn the WP Memory Limit status to green on your System Status page.Step 1 – Locate your wp-config.php file in the root folder of your WordPress installation.
Step 2 – Open the wp-config.php with a text editor program (Notepad or TextEdit) and add the following line of code above /* That』s all, stop editing! Happy publishing. */
Copy to Clipboarddefine ('WP_MEMORY_LIMIT', '256M');xxxxxxxxxx1 1define ('WP_MEMORY_LIMIT', '256M');Simply change the value to the recommended value. For example, 256M.
Step 3 – Save the file and refresh your System Status tab. If the WP Memory Limit turns green, then you have successfully increased your WP Memory Limit.
Method 3: Change Your PHP Memory Limit in .htaccess FileIMPORTANT NOTE: Make sure to back up your .htaccess file before editing. This is another method to change your PHP memory limit. This will not affect the value displayed in WP Memory Limit on the System Status page.Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can』t find it, it may be because it』s hidden. Here』s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files.
Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:
Copy to Clipboardphp_value memory_limit 256M;xxxxxxxxxx1 1php_value memory_limit 256M;Simply change the value to the recommended value. For example, 256M.
Step 3 – Save the file and refresh your website.
PHP Time LimitWhat Is The PHP Time Limit?the PHP Time Limit is the amount of time (in seconds) that your site will spend on a single operation before timing out. This is also to avoid server lockups. The default value for the PHP Time Limit is 30 seconds. When an operation reaches the time limit set, then it will return a fatal error that looks like this
Copy to ClipboardFatal error: Maximum execution time of xx seconds exceeded...xxxxxxxxxx1 1Fatal error: Maximum execution time of xx seconds exceeded...Why Do I Need To Increase My PHP Time Limit?Because the default value is only 30 seconds, you will most likely receive a fatal error when running longer operations. We recommend changing your PHP Time Limit to at least 180 seconds, or to 300 seconds depending on what your host allows.
How To Increase The PHP Time LimitTo increase your PHP time limit, you』ll need to access and modify certain files such as the php.ini, wp-config.php, and .htaccess files. Most hosts won』t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.
For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other methods. For standard users, we encourage you to try Method 2 or Method 3 instead.
Method 1: Change Your PHP Time Limit in PHP.ini FileIMPORTANT NOTE: Many shared hosts prohibit you from having direct access to the PHP.ini file. Only do this method if you have direct access to your PHP.ini file or if you』re on your local host.Step 1 – Locate your PHP.ini file. If you can』t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.
Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):
Copy to Clipboardmax_execution_time = xx;xxxxxxxxxx1 1max_execution_time = xx;Then change xx to your desired limit. For example, 300.
Step 3 – If you created your own PHP.ini file, then add the same code inside it:
Copy to Clipboardmax_execution_time = 300;xxxxxxxxxx1 1max_execution_time = 300;Simply change the value to the recommended value. For example, 300.
Step 4 – Save your changes, and reboot your local host or your server.
Method 2: Change Your PHP Time Limit in WP-config.php FileStep 1 – Locate your wp-config.php file in the root folder of your WordPress installation.
Step 2 – Open the wp-config.php with a text editor program (Notepad or TextEdit) and add the following line of code after 『define(『WP_DEBUG』, false);:
Copy to Clipboardset_time_limit(300);xxxxxxxxxx1 1set_time_limit(300);Simply change the value to the recommended value. For example, 300.
Step 3 – Save the file and refresh your System Status tab. If the PHP Time Limit turns green, then you have successfully increased your PHP Time Limit.
Method 3: Change Your PHP Time Limit in .htaccess FileIMPORTANT NOTE: Make sure to back up your .htaccess file before editing.Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can』t find it, it may be because it』s hidden. Here』s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files on your computer.
Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:
Copy to Clipboardphp_value max_execution_time 3001 1php_value max_execution_time 300Then just put in the recommended value. For example, 300.
Step 3 – Save the file and refresh your website.
PHP Max Input VarsWhat Is The PHP Max Input Vars?The PHP Max Input Vars is the maximum number of variables your server can use for a single function to avoid overloads. The default value of the PHP Max Input Vars is 1000, while the recommended value is 1540. This limitation will truncate some post data such as your menu items which causes issues like your menu items aren』t saving or being left off.
Why Do I Need To Increase My PHP Max Input Vars?You may need to increase your PHP Max Input Vars if you』re running into issues with your menu. If your menu items aren』t saving properly, or if the last few menu items are being left off, this is most likely because your PHP Max Input Vars value is too low. We recommend your PHP Max Input Vars to be 1540 in order to load all the Classic Demo』s menu items.
How To Increase The PHP Max Input VarsLike the other values above, you』ll need to access and modify either the php.ini or the .htaccess files. Most hosts won』t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.
For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other method. For standard users, we encourage you to try Method 2 instead.
767,650 Businesses Trust Avada
Get Avada767,650 Businesses Trust Avada
Get Avada767,650 Businesses Trust Avada
Get Avada,Method 1: Change Max Input Vars in PHP.ini FileIMPORTANT NOTE: Many shared hosts prohibit you from having direct access to the PHP.ini file. Only do this method if you have direct access to your PHP.ini file or if you』re on your local host.Step 1 – Locate your PHP.ini file. If you can』t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.
Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):
Copy to Clipboardmax_input_vars = xx;xxxxxxxxxx1 1max_input_vars = xx;And set it to your desired limit. For example, 1540.
Step 3 – If you created your own PHP.ini file, then add the same code inside it:
Copy to Clipboardmax_input_vars = 1540;xxxxxxxxxx1 1max_input_vars = 1540;Simply change the value to the recommended value. For example, 1540.
Step 4 – Save your changes, and reboot your local host or your server.,Method 2: Change Max Input Vars in .htaccess FileIMPORTANT NOTE: Make sure to back up your .htaccess file before editing.Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can』t find it, it may be because it』s hidden. Here』s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files on your computer.
Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:
Copy to Clipboardphp_value max_input_vars 1540xxxxxxxxxx1 1php_value max_input_vars 1540Simply change the value to the recommended value. For example, 1540.
Step 3 – Save the file and refresh your website.

Updating Avada from Older Versions

Why you should update your theme and plugins regularlyA major reason to keep your WordPress theme and 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.
Pre-Update Tips
Before processing any update, make sure to take a full site and database backup. That will ensure you』re able to revert to a working point in your site if anything unexpected happens.

It』s also very important that you ensure your server limits are at least at the required minimums for the update/theme install to complete seamlessly. Read our Requirements for Avada doc for more information.

When updating from old versions of Avada, we strongly recommend a staggered update path. Below, we』ll guide you through one major theme update at a time. This will make the process as smooth as possible for you. At the end of each section, there will be a link to download each theme version, as required for the update path.

Check our detailed Important Update Information Archive document to find noteworthy details for any specific updates between your current version and the latest Avada version.
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

Avada 3.9 and older: If you』re below version 3.9, start with the steps in this section.

Avada 3.9.X: If you』re at version 3.9.X, start with the steps in this section.

Avada 4.0.X: If you』re at version 4.0.X, start with the steps in this section.
Avada 5.9.1: If you』re at version 5.9.1, start with the steps in this section.,Updating From Avada 3.9 And OlderRegardless 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. For info on what』s new to this theme version, visit the What』s new in Avada 3.9 page!,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 detailed information on the 3.8 update, please click here.

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.
Note: Since you』ll be updating with the Avada 3.9.4 files manually, only method #2 and #3 will work from that post.
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.
767,669 Businesses Trust Avada
Get Avada767,669 Businesses Trust Avada
Get Avada767,669 Businesses Trust Avada
Get Avada,Updating From Avada 3.9.XWhen 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. For info on what』s new to this theme version, view the What』s New in Avada 4.0 page!,If you haven』t checked the Pre-update Tips section, click here for that important information.
In Avada 4.0.X the most notable change will be the migration from the old Avada Theme Options to the new Avada Theme Options.
IMPORTANT NOTICE: Before processing this update, be sure to take a full site and database backup. That will ensure you』re able to revert to a working point in your site if anything unexpected happens.To be sure the Theme 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 Theme 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.

SPECIAL NOTE FOR WPML USERS: If you』re using WPML, you』ll want to be sure you』re updated to the latest version of the plugin so the migration completes for all languages. There was a conflict in a previous WPML version which caused the Theme Options migration to get stuck midway through. This was fixed in their plugin, so using the current version will ensure you』re in the clear.,Updating From Avada 4.0.XIf your current theme version is Avada 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. For info on what』s new to Avada 5.0, click here.
If you』re not at 4.0.X yet, please reference the appropriate section above for your current theme version, before proceeding.
If you haven』t checked the Pre Update Tips section from above yet, click here for that important information.
IMPORTANT NOTICE: Before processing this update, be sure to take a full site and database backup. That will ensure you』re able to revert to a working point in your site if anything unexpected happens.Since the new Fusion 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, theme options, Fusion Sliders, Revolution Sliders and LayerSliders.
Note: It will not automatically convert shortcodes from any custom post types you may have or from other plugin』s custom post types that may be in use on your site. For information on how to manually include those post types in the Avada conversion process, click here to view our guide.
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 Fusion Builder plugin is installed and activated.,Updating From Avada 5.9.1If your current theme version is Avada 5.9.1, then your next stage in the update will be the latest version of Avada. The current latest version is Avada 7.3, which includes a new registration system. For more details on that, please see the Changes To Registration With Avada 7.3.
If you haven』t checked the Pre Update Tips section from above yet, click here for that important information.
IMPORTANT NOTICE: Before processing this update, be sure to take a full site and database backup. That will ensure you』re able to revert to a working point in your site if anything unexpected happens.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.,Getting Additional Help When NeededHow To Update The Theme
To register an account and register your purchase to access theme support, please click here.

If you already have registered and need assistance, please create your support ticket here.
Purchases made before September 1st, 2015 are eligible for our Avada Grandfathered support. More information on Grandfathered support can be found here.
If your support account has expired, you can find information on renewing that here.

Avada Changelog

Avada is constantly being updated with new features and adjustments. You can always view the most recent update information in the changelog in the changelog.txt file inside the theme zip file. You can also view the full changelog below.
For mobiles, opening the changelog in a new tab will be more convenient.

How To Install Avada Via FTP

There are two ways you can install the Avada Website Builder. You can install it via FTP, which is what will be outlined in this article, or you can install it via WordPress. Before you can install Avada, you will need to first download the necessary files from ThemeForest. Continue reading below for more information on theis installation methoid, and watch the video for a visual overview.,Where To Locate The Download FilesStep 1 – Login to the ThemeForest account that purchased Avada, navigate to your 『Downloads』 tab, and then locate your Avada purchase.
Step 2 – Click the 『Download』 button and choose to either download the 『Installable WordPress file only』, which is just the WordPress installable file package, or choose to download 『All Files & Documentation』 which is the full Avada Website Builder package. For installing Avada, only the Installable WordPress package is neccesary. If you want to install a Child Theme, you can find that in the All Files & Documentation zip file.,The FTP Installation ProcessStep 1 – Log into your server installation via FTP. You can use software such as Filezilla for this.
Step 2 – If you have downloaded the Full Package from ThemeForest, please unzip the master Avada.zip file and then unzip the secondary Avada.zip file which will give an Avada folder. If you download the Installable WordPress file only, simply unzip this, and you will have the same Avada folder.
Step 3 – Using the FTP client, upload the extracted Avada folder to the wp-content > themes folder on your server. Make sure the folder name is unchanged, so it』s called 『Avada』. This will take a few minutes, depending on your connection speed and your server.
Step 4 – Log in to your WordPress Dashboard and navigate to Appearance > Themes and clicking the 『Activate』 button, for the Avada theme.
Step 5 – Once activated, you will be redirected to the Welcome Screen. You』ll see a prompt to register Avada and then install the required plugins, which are the Avada Core and Avada Builder plugins. Click here to learn how to install Avada』s required plugins.
View how to install via WordPressWatch How To Install a Child Theme

Avada Child Theme

IMPORTANT NOTE: If you are having issues with your Child Theme, particularly after updating to Avada 7.2, please see this explanation FAQ. In short, it』s to do with the style sheet being moved, and so a new snippet of code is required.A WordPress child theme allows you to apply custom code changes to your site. Using a child theme ensures that all your customizations will not be overwritten even when you update the parent theme. Continue reading below to learn how to setup your own child theme, and watch the video for a visual overview.
SUPPORT POLICY ON CHILD THEMES: While child themes are a great way to add custom changes to Avada, there are generally used to customize core code from the parent theme. Because of this, please be aware that customizations of this nature fall outside our scope of support and we will be unable to assist you with issues that may arise from it.Overview
What Is A Child Theme?

Downloading and Installing the Avada Child Theme

How To Download Avada Child Theme

Methods Of Modifying A Child Theme

Useful Documentation On Child Themes
What Is A Child Theme?A child theme is a theme that has all the functionality and styling of another theme, called the parent theme, which in our case is Avada. Child themes are the recommended way of modifying the code of an existing theme, because a child theme preserves all custom code changes and modifications even after a theme update.
If you modify code directly in a parent theme, and then update the parent theme, your changes will be lost. Always use a child theme if you intend modifying core code. Child themes can be used for a number of things, such as custom CSS applications, template file modifications, and custom PHP functions and/or hooks. There are a couple of methods to modify a child theme. Child themes don』t guarantee that an update of custom code on the parent theme will not require further maintenance. This is especially true if you copy files from the parent theme to your child theme.

Downloading and Installing the Avada Child ThemeBefore anything else, you must first download and install the Avada child theme to begin making your customizations. The Avada child theme comes with downloading Avada』s Full Package from ThemeForest, and the method of installing it is exactly the same as installing the Avada theme. Please follow the detailed steps below on how to download and install the Avada child theme.
How To Download Avada Child ThemeStep 1 – Login to your ThemeForest account and go to your Downloads tab.
Step 2 – Locate your Avada purchase, and click Download. Choose the 『All Files & Documentation』 option.
Step 3 – Once the .ZIP file is finished downloading, locate it on your computer and extract it. You will then have a folder called Avada_Full_Package.
Step 4 – Navigate to Avada_Full_Package > Avada Theme and you will see an Avada.zip file and an Avada-Child-Theme.zip file.
Step 5 – Before installing the Child Theme, you must first have Avada (the parent theme) installed. You install the child theme using the exact process of installing the parent theme. You can choose to install the theme zip files via WP upload or via FTP upload.
Methods Of Modifying A Child ThemeThere are a several methods you can use to modify a child theme, and we』ll be explaining 3 methods below. These methods are copying files from a parent theme, pluggable functions, and actions and filters. To learn more about each one, please continue reading below.
Method 1: Copying Files From Parent ThemeCopying files from the parent theme to a child theme is a common method to make code customizations. This is the easiest method available, but there are limitations to it. Due to the limitations, we recommend only copying the files inside the templates folder from the parent theme into the child theme.

You can only copy some files to the child theme. In Avada, we have made a decision to make sure that core logical code which can break the theme is not able to be copied into the child theme. This includes the files inside the includes folder.

It is not update-safe (sometimes). Whenever we make major changes to a certain file e.g. header.php in the parent theme, you』ll have to copy the theme file from parent theme again and apply the customizations again. If you don』t do this, there』s a chance that the related feature might not work anymore.
Method 2: Pluggable FunctionsPluggable functions are PHP functions that can be changed inside a child theme or a even a plugin. If a function is wrapped inside a function_exists call within the parent theme, you can create the same function in the child theme which will override the original function from the parent theme, because child theme functions are loaded first.
Example of a function override inside the Child ThemeTo change the rendering of the Page Title Bar, you can override Avada』s avada_get_page_title_bar_contents function, which is located in Avada/includes/custom_functions.php. The function definition looks like this:
Copy to Clipboardif ( ! function_exists( 'avada_get_page_title_bar_contents' ) ) {
/**
* Get the contents of the title bar.
*
* @param int $post_id The post ID.
* @param bool $get_secondary_content Determine if we want secondary content.
* @return array
*/
function avada_get_page_title_bar_contents( $post_id, $get_secondary_content = true ) {
if ( $get_secondary_content ) {
ob_start();
.
.
.

return array( $title, $subtitle, $secondary_content );
}

}x 1if ( ! function_exists( 'avada_get_page_title_bar_contents' ) ) {2 /**3 * Get the contents of the title bar.4 *5 * @param int $post_id The post ID.6 * @param bool $get_secondary_content Determine if we want secondary content.7 * @return array8 */9 function avada_get_page_title_bar_contents( $post_id, $get_secondary_content = true ) {10 if ( $get_secondary_content ) {11 ob_start();12 .13 .14 .15 16 return array( $title, $subtitle, $secondary_content );17 }1819}Simply copy the function to the functions.php of the child theme, which will override the parent theme』s one. Once done, you can modify it to meet your needs.
Copy to Clipboardfunction avada_get_page_title_bar_contents( $post_id, $get_secondary_content = TRUE ) {
// Place your code here.
.
.
.

return array( $title, $subtitle, $secondary_content );
}xxxxxxxxxx8 1function avada_get_page_title_bar_contents( $post_id, $get_secondary_content = TRUE ) {2 // Place your code here.3 .4 .5 .67 return array( $title, $subtitle, $secondary_content );8}Method 3: Actions and FiltersThe correct and safest way of updating or modifying theme functions within a child theme is using actions and filters. Apart from the actions and filters built-in within Avada, you can use the default WordPress actions and filters to modify the theme』s functionality.
A simple example would be changing the image size generated for blog large layout thumbnails in the Avada theme. The correct way to re-register within the child theme is to use after_setup_theme action in the child theme functions.php, remove the image size and then re-register the image size.
Example of an ActionCopy to Clipboardadd_action( 'after_setup_theme', 'my_child_theme_image_size' );
function my_child_theme_image_size() {
remove_image_size( 'blog-large' );
add_image_size( 'blog-large', 1000, 500, true );
}xxxxxxxxxx5 1add_action( 'after_setup_theme', 'my_child_theme_image_size' );2function my_child_theme_image_size() {3 remove_image_size( 'blog-large' );4 add_image_size( 'blog-large', 1000, 500, true );5}Useful Documentation On Child ThemesIf you』d like to learn and read even more about child themes, please follow the links below.
WordPress Codex on Child ThemesWordPress Developers Handbook: Child ThemesHow To Create A WP Child Theme video by WPBeginner.com

How To Install Avada Via WordPress

There are two ways you can install the Avada Website Builder. You can choose to install it via WordPress, which is what will be outlined in this article, or alternatively, you can install it via FTP. Before you can install Avada, you need to download the necessary files from the ThemeForest account Avada was purchased from. Continue reading below for more information, and watch the video for a visual overview.,Downloading The Installation Files From ThemeForestThe first thing to do is to download the installation files from ThemeForest. There are two packages available, as you can see in the screenshot below – All files and documentation, and the Installable WordPress file only. The Full Theme Package has additional files such as the Child Theme zip, Revolution and Layer Slider documentation and the classic demo .PSD files, while the Installable WordPress file contains only the files you need to upload to WordPress. For full details, see the What』s Included With Your Avada Purchase doc.,Where To Locate The Download FilesStep 1 – Log in to your ThemeForest account and navigate to your 『Downloads』 tab and then locate your Avada purchase.
Step 2 – Click the 『Download』 button and choose to either download the 『Installable WordPress file only』, which is just the WordPress installable file, or choose to download 『All Files & Documentation』 which is the full Avada Website Builder package.,The Installation ProcessStep 1 – Navigate to Appearance > Themes from the WordPress Dashboard.Step 2 – Click the 『Add New』 button on top of the page, then the 『Upload Theme』 button.Step 3 – Click 『Choose File』 and find the theme files you』ve just downloaded. If you』ve downloaded the installable WordPress file, then you do not need to unzip the file. If you』ve downloaded the Full Theme Package, you have to unzip the master Avada.zip file, therein you will see a secondary Avada.zip file. This is the one you select to install.
Step 4 – Once the file has uploaded, click the Activate link.
For instructions on how to install via FTP, go here.Having issues with Installation? Go Here.,Register Your Avada PurchaseOnce you activate Avada inside WordPress as the default theme, you will be redirected to the Avada Welcome Dashboard. You』ll be prompted to register Avada using your purchase code, so that you can then install the required Avada Core and Avada Builder plugins.
See this document on how to register Avada.See this document for more information about the required and bundled plugins.See this document for more information on importing prebuilt websites.,Troubleshooting『Are You Sure You Want To Do This?』 ErrorIf you get the 「Are You Sure You Want To Do This」 message when installing Avada.zip file via WordPress, it means you have an upload file size limit that is set by your host. If this happens, please install the theme via FTP or contact your hosting company and ask them to increase the limit.

Avada v4 Migration

IMPORTANT NOTE: The new Avada Theme Options is only available on Avada version 4.0+, this help file is applicable to anyone updating from a very old version of Avada (pre Avada 4.0).The new Theme Options panel that』s included with Avada version 4.0 is a truly extensible and powerful options framework for Avada. Because we』re using an entirely new Theme Options panel, it is necessary for your previous Avada installations to be migrated.
When updating from an older version of Avada to version 4.0, your current theme option values will be copied and stored in your database for safe keeping. In doing this, no data is lost during migration. The extra copy of theme options is then migrated over so that you can utilize the new options panel. Always make sure you backup your current theme folder before you upgrade. Updating Avada from previous versions to version 4.0 is a simple process and will be automatically run the first time you visit your dashboard after updating the theme files.
View screenshot here of what you will see when the migration is complete. Notice the LARGE RED BUTTON telling you to update the Fusion Core plugin.
How To Fix Migration ErrorsIn very rare cases, you may encounter issues with the update script. This usually occurs when your server has extremely low PHP settings. In case this happens to you, please continue reading below to learn about what to do when your migration fails.
How To Trigger Migration ManuallyStep 1 – Navigate to the Avada > System Status tab.
Step 2 – Under the Avada Versions section, click on the 『Trigger Data Migration』 link. View screenshot here.
Step 3 – Once you click the Manual Migration link, you will be redirected to the Migration Screen. Please wait until the data migration is finished.
Step 4 – When the data migration is finished, click the 『Take Me To Theme Options!』 button to be redirected to your new Theme Options panel.