Genesis Club Pro v4.7 and later revisions include version 5 of the LayerSlider.
What Has Changed With The Layerslider?
In this release I have done less repackaging of the Layerslider and have opted to use its own method of storing the sliders which is the database_prefix_layerslider table instead of an entry in wp_options. In previous versions I had re-written the plugin to allow it to not have to create new database table. But it had become too labour intensive for me to have to re-write large chunks of the plugin every time the Layerslider author issued an update.
Therefore I have reverted to using the author’s method of holding data – which (unfortunately) requires the plugin to create a new database table. If your server does not allow plugins to create new database tables, the Layerslider portion of the plugin will not work.
Clearly, using wp_options is my preference however I am trading off speed of incorporation of new versions of Layerslider against the reliability of the upgrade process for this release.
In order to preserve existing sliders the plugin upgrade processes attempts to create the new database table and then copy the sliders from the wp_option called genesis_club_sliders to the new table. On most servers this will work. However it will fail in a number of circumstances and in these cases manual intervention is required.
Before The Upgrade
Before upgrading, export all sliders. This will create a JSON file on your desktop. This serves as a backup and an alternative way of loading the sliders if required.
During The Upgrade
Run the plugin upgrade. Wait until the message reads Plugin has been updated FOLLOWED BY Plugin has been reactivated. If you do not wait for BOTH messages and click away too soon then sliders will not be migrated.
After The Upgrade
On the menu click on Genesis Club Sliders. If your sliders have not been migrated, then check if the database_prefix_layerslider table exists. You may need to ask your host to help do this. Please also try deactivating and then reactivating the plugin, this might resolve the issue.
How To Create The Layerslider Table Manually
If the plugin was unable to create the database table, then you will need to create the database table manually. Go into your database admin tool (e.g. phpMyAdmin) and in the SQL window, create the table with the correct prefix. For example, on most systems the table name will be wp_layerslider.
CREATE TABLE database_prefix_layerslider (
id int(10) NOT NULL AUTO_INCREMENT,
author int(10) NOT NULL DEFAULT 0,
name varchar(100) NOT NULL,
slug varchar(100) NOT NULL,
data mediumtext NOT NULL,
date_c int(10) NOT NULL,
date_m int(11) NOT NULL,
flag_hidden tinyint(1) NOT NULL DEFAULT 0,
flag_deleted tinyint(1) NOT NULL DEFAULT 0,
PRIMARY KEY (id)
Then deactivate and reactivate the plugin again. This should now be able to copy the sliders to the new table.
If this fails then double check you used the correct database prefix when you created the table.
Manual Slider Import
If the sliders did not copy across, then perform a manual import. Go to Genesis Club Sliders and click the Choose File> button browse to the JSON file you downloaded earlier, then press the Import button.
When the layerslider was created it was unusual to set up security so WordPress could not create tables. However in today’s more security conscious environment it is more common.
The new release, v4.7.2 will also include a check for the presence of the new database table. If it is missing it will flag an error so the user can take action and create the table.
In the meantime I have withdrawn the 4.7.1 upgrade so anyone still on 4.6 will have a smoother upgrade path to 4.7.2.