Important Update Info
With each new Avada update comes incredible new features, new options, code improvements and fixes. Our team takes the utmost care in creating updates and ensuring everything is fully tested by our team as well as a large group of beta customers. It is important that we communicate to our customers any important items that need to be taken into consideration when updating. This post is dedicated to relaying that information to you any time a new major version of Avada is released.
Avada 5.7.2 (Released on December 3rd, 2018)
Avada 5.7.2 Important Update Information
1. Fixes XXS Security Issue In Bootstrap JS Fixed
For the release of Avada 5.7.2 we have fixed a XXS security issue pertaining to Avada versions 5.7.1 and below. The fix is for the bootstrap JS libraries that are used in Avada and is listed in our Changelog.
Our development team was alerted to and thereby took action to check and verify the bootstrap vulnerability. Once accurately verified, our team took steps to apply the fix to Avada 5.7.2.
Have a full read about it in our blog: XXS security fix in Avada 5.7.2.
2. Compatibility With WordPress 5.0
WordPress version 5.0 has been released on
November 19th, November 27th, 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.
Avada 5.7 Important Update Information
1. Fusion White Label Branding 1.1 Released
With Avada 5.7, we have updated Fusion White Label Branding to version 1.1, introducing a bunch of new and highly requested features, like import/export, section and overall option reset and options to disable various admin menus.
2. Container Publishing Settings
Avada 5.7 introduces a new and very versatile option to Fusion Builder container elements: Container Publishing Status. It allows users to set Draft or Published status on individual containers per page. If you want to prepare a special section for a later release on one of your live pages, this will help you to preview the section, without visitors seeing it. For promotional and other purposes, we have also added Published Until and Publish After settings, which let you choose an end or a start date and time when a container should be auto published. You can read more about it on the Container Element Page.
3. Header Color And Transparency
This update introduces header transparency on mobile devices, which has been a long requested feature. While adding this for your convenience, we have also reworked our desktop header color and transparency settings in Fusion Page Options, for consistency reasons. That means, moving forward, you can set both the color and transparency level of the desktop header through just one color picker, like you are already used to in Theme Options. The same pattern also applies to the mobile header. Already set pages are auto converted to this new format, so you don't have to make any manual edits.
4. Menu Icons In Vertical Menu Widget
Our vertical menu widget can now display custom menu icons you have set in the Avada Menu Options. This is new to Avada 5.7, so if you were using a menu within the vertical menu widget, that already had icons set, they will now be displayed on the front end.
5. Image Element Glow And Dropshadow
Avada 5.7 comes with a new blur option, which lets you fine tune the amount of highlight you want to set through glow or drop shadow on the Image Element. With this update, we have also fixed the style color option for drop and bottom shadows. They will now appear in the color that is set as the style color, which could lead to slight visual changes on existing pages.
6. Post Title Color Fix
In Avada 5.7, we have fixed the post title color option on blog archive pages and for the blog element. Previously the set color did not change there for post titles. This could lead to slight visual changes after the update.
7. Fusion Slider Settings Moved in Database
In previous versions of Avada, the Fusion Slider settings have been stored in the
wp_options table of WordPress. That simply has been the case, because Fusion Slider was released, before WordPress introdiced
wp_terms_meta table in WP 4.4. To improve the table management and also option deletion process, when sliders are deleted, we move the Fusion Slider options to the
wp_terms_meta table in Avada 5.7. This is done through an automatic migration on update, so you don't have to do anything.
When exporting or migrating a site, it is important that you don't "mix" a pre Avada 5.7 site with a site on Avada 5.7 or later, to make sure you don't have Fusion Slider option entries in both database tables, or worse just in the
wp_options table (old), and not the
wp_terms_meta one (new).
If you have problems with your Fusion Slider settings after update please refer to our Fix Missing Fusion Slider Settings After Update article.
8. Avada And Gutenberg - Continued Compatibility Progress
Here at ThemeFusion HQ, we constantly strive to evolve Fusion Builder, by adding new features and dynamic solutions to supercharge your workflow. We have big plans for Fusion Builder in the coming months and years, and as a team, we are excited to deliver these updates to our wonderful customers.
While Fusion Builder continues to set new benchmarks for usability and and functionality, we are also aware, that the WordPress core development team likewise is hard at work to improve the default editing experience of WordPress. The classic editor has come a long way, but it is time for an improved WordPress native post editing experience. This is why the new Gutenberg editor will be released with WordPress 5.0. The new WP editor is still positioned as a beta plugin and has not matured enough to make it into core, but eventually it will be merged in.
We know that our user-base prefers the power and convenience of Fusion Builder to create and edit their page and post content, but we also believe that we should make it easier for everyone to try out Gutenberg and to use it side by side with the Avada Fusion Builder. For this reason, we have added several small helpers to Avada 5.7. By default, if you have the Gutenberg plugin enabled, the Fusion Builder will load on edit pages of post types where you have it enabled. Also, we have added a Fusion Builder edit link to the WP native new/edit dropdowns, and we have added a new button on top of the Gutenberg main panel, that lets you easily switch to the Fusion Builder.
If you want to try out some of our elements in Gutenberg, you are free to do so: we have added our element generator to the Gutenberg classic block, so that you can easily check it out.
Our team will stay on top of the Gutenberg development cycle as it develops to ensure that Avada users get the best out of WordPress and Avada.
General Update Information
1. Always 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 Fusion Theme Options on the Backup tab in Appearance > Theme Options > Backup.
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 Theme Cache, Browser Cache, Server Cache And Plugin Cache
It is always recommended to reset all caching systems after an update, including theme cache, your browser, plugin (e.g. W3 Total Cache), and server cache. Visual issues may happen and more often than not, its caused by caches, and they need to be emptied. Each browser allows you to remove cookies, history and other data. If your theme or Fusion 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. View our general cache information that describes the various forms of cache and how to clear them.
For Avada versions 5.1 and higher there is a special button in Theme Options, called "Reset Fusion Caches" that lets you reset the theme cache. You can find it by going to Avada > Theme Options > Advanced > Dynamic CSS & JS.
5. Update The Child Theme
If you have copied template files from parent theme to child theme. Please make sure to revert to parent theme first to confirm if the issue exists there too. If it doesn't, please update the templates copied to child theme with the parent theme.
6. 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. Our Fusion Core plugin is the only required plugin and it has to be installed and activated for theme features to work. Make sure you are always using the most recent version of the Fusion Core plugin. You will be prompted to install it upon installing or updating your theme. If you dismiss the prompt or do not see it, then you can go to Appearance > Install Plugins page and install the plugin that way. Every time you update the theme, the plugin also needs updated.