If you encounter errors during or after importing a prebuilt website, please see below for possible solutions. If you don’t find what you’re looking for below, please don’t hesitate to submit a support ticket to our support team.
Missing websites on the Websites’ page
If the websites aren’t appearing on the Avada > Websites page, then your purchase may not have been registered via Token Registration. Please register your product first to access the Prebuilt Avada Websites.
Slider Alias or ID Not Found For Layer or Revolution Slider
If you already have sliders made, or something unexpected occurs during the import due to low server memory, it’s possible that our website sliders may not be assigned to the pages. You may see an error such as Revolution Slider Error: Slider with alias Avada_Full_Width not found or LayerSlider cannot be found. Sliders are applied by the Slider ID. Each slider gets its own unique ID and they are given in numerical order. If you open up a page after importing the content and you see an error like that, you only need to edit the page and assign the slider to the page. To verify you have the sliders, go to the Layer or Revolution Slider section of your admin to see them listed. If you do not see them, then you can import the sliders separately
Website import failures
If your prebuilt website import fails, there will be a notice and some info on what may have gone wrong in a popup. You’ll find some suggestions of what to check first in that same popup. For example Website import failed. Please check for PHP limits in red on the System Status page. Change those to the recommended values and try again. You’ll always want to check your System Status page first to see if there are any low limits in red. If you see that, increase them to the recommended limit and then try the import. Generally your web host will be able to take care of increasing low limits for you. More info on changing these specific server limits can be found here.
For details on Avada required minimums, please see our post here.
You may also find the below posts useful if you’re having any of the below errors:
Prebuilt Website Content Will Still Not Import – Try Alternative Methods
If your host will not make changes, or you cannot get the website content to import, then please try our Alternative Prebuilt Website Import Method.
Website Content Duplicated
With the Prebuilt Website importer in Avada 5.2 and above, it’s not possible to import duplicate content (unless the website content was imported in Avada 5.1.6 or before and then you imported again in 5.2+). However, if you do have duplicate website content from versions before 5.2 or due to existing website content before importing again on 5.2, you can use the below methods to address this:
Method 1: WP Reset Plugin – This plugin is the fastest way to get rid of content. However, it will remove all content from your database and leave the default theme activated. It does not remove plugins, but will deactivate them and remove all pages, posts, menus, sliders, widget data, Global Options, etc. It removes all the content from your database. Only do this if you are planning to start your site freshly from a new WordPress install/new Prebuilt Website import. Click here to download the WP Reset plugin.
Method 2: Manual Removal – This method will take longer and simply involves manually removing duplicate items. For example, go to the Appearance > Menu and delete any duplicate items one by one. It will be the same process for pages, post, sliders, images etc.
Prebuilt Website Blog Posts Show Up In Your Blog Feed
Most of our prebuilt websites contains published blog posts. If you import on a live site, plugins like JetPack will notice new posts and push them out into your blog feed. Please disable any plugin that may do that before you import. After the import, you can remove the posts or save them as drafts then turn your plugin back on.