Avada 5.4.2 Important Update Information
1. Support of WooCommerce 3.3 Requires Avada 5.4.2
WooCommerce 3.3 is (was) released on Jan 30th, and Avada 5.4.2 must be used if with it as it offers full compatibility with this new version of WooCommerce. As our userbase knows, we always make sure that Avada is working nicely with the latest version of WooCommerce, and that we keep adjusting our codebase continually in order to use state of the art architecture, supporting newest features.
A lot of things have changed in this new version of WooCommerce. The “Display” options page e.g. which has previously been under the “Product” tab in WooCommerce Settings, is now in the customizer. WooCommerce 3.3 now offers a product column setting for the first time there. Since Avada has been offering this option since a long time, and since we offer 3 different column options (main shop page, archive pages and cross-/upsell-product areas), which offers a lot more flexibility for our users, we’ll stick to these already well-known options which you find in our Theme Options panel on the WooCommerce tab, just as per usual.
Under the hood, WooCommerce made a lot of changes to template files and added a bunch of new functions that should be used from now on. This helps cleaning up code and makes WooCommerce staying on top of new and upcoming programming trends. At the same time some old functions have been deprecated in favor of the new ones, to make sure the community is staying up to date with WooCommerce.
All of this has been taken care of in Avada 5.4.2 for your convenience!
2. Avada drops support for the outdated WooCommerce 2.6.x versions
Since Avada 5.4.2 now offers support for the brand new WooCommerce 3.3 version, we decided that this was also a good time to do some housekeeping. We have always been supporting several versions of WooCommerce at the same time, to make updating to latest versions an easy and seamless process for our users, without forcing them to update within a few days. We’ll stick to this well-established course, and thus Avada 5.4.2 will support every WooCommerce version from 3.0 onwards. That does mean that we drop support for the old and outdated 2.6.x versions. Why these versions? Because 2.6 was the last minor version before the 3.0 major release, so we are dropping only one minor now. Also, the release of 2.6.14 was at the beginning of February 2017, so almost everyone should be on one of the 3.x versions by now. In addition, as said above, WooCommerce 3.3 has deprecated some older functions and changed quite a few template files. So, it became necessary to cut support for 2.6.x versions to make sure we are not using deprecated functions in Avada and to clean up our WooCommerce support code.
If you have not updated your WooCommerce install to 3.x or the new 3.3, it is now the best time to do so. Once WooCommerce is up to date, you can update Avada anytime to 5.4.2 and will get the best working experience yet.
3. Updating to Avada 5.4.2 before WooCommerce 3.3 is released when you have template overrides in a child theme
In case you are using a child theme and are using full template overrides, we recommend waiting with the theme update until WooCommerce releases its version 3.3. Reason for this is, that otherwise you will have to change the folder structure in the child theme, and that only until WooCommerce has finally released.
If you nevertheless choose to update Avada right away, please move your templates from woocommerce to woocommerce/compatibility/3.2/. 3.2 folder does look strange, but is correct in that case, as once WooCommerce has been released, that is where compatibility for older versions will be.
4. Updating Avada from 5.4.1 to 5.4.2
When updating Avada to 5.4.2 from Avada 5.4.1, please make sure that you have the only available patch, with title “Fixes PHP fatal error when Fusion Builder is active without Avada.”, applied.
Updating using the auto update functionality or a direct FTP update won’t be of any issue. But if you want to upload the theme, using the WP theme uploader, you would have to remove old theme prior to that. And in that case, the patch needs to be applied first, as you would get a PHP fatal error otherwise, and the site would no longer be accessible.
This could then be resolved again, by logging into your site via FTP and simply renaming the fusion-builder folder in plugins folder to a different name. That way, the site can be accessed again as Fusion Builder plugin gets auto deactivated. Then you can install Avada, rename Fusion Builder folder back, and finally reactivate Fusion Builder.
Obviously it is better though, to either use auto update for the theme and/or to make sure the patch is applied prior to update, which resolves this inconvenience for good.
5. Thank you 2017, Bring On 2018!
Avada 5.4 is an end of the year gift to our customers, one last awesome update full of value added features for you! We’ve included 3 premium plugins worth over $100 for free! ACF Pro, Convert Plus & Fusion White Label Branding! In addition, we’ve included 3 new professionally designed demos ready rot import however you’d prefer, full, partial, single pages, etc.
WHAT DOES THIS MEAN FOR YOU?
One last awesome update for 2017! A promise from us to continue and add more value to Avada so this amazing product can continue and change the workflow of hundreds of thousands of people who use it daily to build incredible websites. Bring on 2018, the best year to come!
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 Theme Options > Advanced > Dynamic CSS & JS.
5. Update 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.Click Here To Find Out How To Update Your Theme