Kreatura Support Center

You can find the Item's requirements in its documentation or on the item page on Envato marketplaces. More details are in the "Installation & Updates" section.

We are working really hard to test everything and keep the plugin as bug-free as possible. However, there is no perfect software and our products are not an exception either. We strongly recommend you to use the most up-to-date version of the Item before reporting any issues. We are relying on your feedback and there is a good chance that we have already fixed an issue you may experience. You can check the last update date on the Item's page on Envato marketplaces.

Some outdated plugins and themes can cause issues in really unexpected ways, and you should have up-to-date versions of every plugin and theme you use. Most of the issues caused by 3rd party solutions, and there is a good chance that their authors have already released updates to fix the problems you may have.

Most of the issues that our customers are having are not problems with our Items, usually they are related with 3rd party components. We are trying our best to workaround common issues with 3rd party components, but it is not always possible. If you read this FAQ section carefully, you will most likely find the answer or solution that you are looking for.

If you did not find the answer you are looking for, we would like to recommend you to try to search for any related issues in our ticket system. Our ticket system is currently under development and will be available soon.

Components not following the WordPress standards may interfere with other plugins in unexpected ways and can be difficult to find. If you are having an appearance issue, please report it to us and we will check it. In case of experiencing issues with features or functionality, you should try to temporarily disable every other plugins and switch to another theme (the default one is recommended). If it solves your problem, it is related with an other component and you should try to find the one by re-enabling them one after another and keep watching when you can reproduce the issue. Please note that in a multisite installation there can be further plugins on the network dashboard that your sub-site may not list them by default. Once we know the source of the problem, we can probably fix it or give you instructions to workaround it.

Regular license

• Purchasing the Item is for personal purposes without using it commercially. Webshops and ads on your site is not considered commercial use, see details below.
• As a freelancer buying the Item is on your client's behalf with the intended use of the previous point.
• Having a multisite environment where the network-sites is generally have the same role and content. For example, separate sub-sites for localized contents.
• The Item is used for preview purposes only and it is not actually part of the larger work you are for sale.
• Modifying the Item is for your own personal use only.

Extended license

• The Item is part of a larger work for sale.
• Offering commercial services where the Item is used as part of your solution and only available for paying users.
• Having a multisite environment is where the network-sites have different role or content.

More information with examples

For more information, please read the licensing FAQ on Envato marketplaces.

Things you cannot do with the Item

Please also read the third entry from this section about the things you cannot do with the Item

Webshops and ads on your or your client's site is not considered commercial use. Envato defines the cases of commercial use where you have direct benefit from the purchased Item, for example, selling it as a part of your larger work (themes, templates, etc) or using it in a way that is only available for paying users and is an essential part of your commercial services.

Check our Envato's Licensing FAQs for more details, they have examples for almost every scenarios.

• An End Product is one of the following things, both requiring an application of skill and effort.
  
  • For an Item that is a template, the End Product is a customised implementation of the Item.
  • For other types of Item, an End Product is something that incorporates the Item as well as other things, so that it is larger in scope and different in nature than the Item.
• You can modify or manipulate the Item. You can combine the Item with other works and make a derivative work from it. The resulting works are subject to the terms of this license. You can do these things as long as the End Product you then create is one that’s permitted under clause 3.
• This license is a “single application” license and not a “multi-use” license, which means that you can’t use the Item to create more than one unique End Product.
• You can’t re-distribute the Item as stock, in a tool or template, or with source files. You can’t do this with an Item either on its own or bundled with other items, and even if you modify the Item. You can’t re-distribute or make available the Item as-is or with superficial modifications.
• Although you can modify the Item and therefore delete components before creating your single End Product, you can’t extract and use a single component of an Item on a stand-alone basis.
• You must not permit an end user of the End Product to extract the Item and use it separately from the End Product.

Definitions: The Item is what you purchase from Envato marketplaces. The End Product is the customized work what you build with that Item.

For more information, please read the licensing FAQ on Envato marketplaces.

Envato does not offer any multi-use / developer license yet, but they are planning to introduce it. Envato is the operator of the marketplaces, we do not have any control over the available licenses and do not know their exact plans.

We are an exclusive author, we cannot do business behind Envato, thus we cannot offer you any special deals. Currently, the only solution is buying separate licenses for each site or service you would like to use the Item with.

In a case where your network-sites have generally the same role and content (for example: offering the same content on localized sub-sites), you can use the item with a regular license.

You can if you develop a WP theme for ThemeForest with the following conditions:

• You need to purchase an extended license per themes after every Item you include in your work.
• You need to handle the support requests after the included Items.
• You cannot offer the plugin as a stand-alone item.
• You cannot provide an Item Purchase Code for your customers.
• Updating the plugin is your own responsibility.
• You need to follow Item-specific instructions in our documentation for developers (if any).

Our developer documentation deals with these rules in a deeper level, please read them to have a better understanding why it is important for us. You can include our Items in your work without a written permission by following these rules. Just reference to this entry if an Envato reviewer ask about permissions.

If these rules are not suitable for you, please contact us at contact@kreaturamedia.com, and we can discuss the details.

Please note, we only allow to bundle LayerSlider in WordPress themes, which will be sold on ThemeForest explicitly.

You cannot re-distribute or make our Items available in any form, even if you modify them. You can't use a subset of our works either, your derivative works are also subject to the license terms. Please read the "Things you cannot do with an Item" section of this FAQ for more information.

However, we can team up and work together in a cooperation if you have a nice idea. In this case, we would like to hear from you.

For personal use only, you can modify the plugin and use it in a way you want as long as it complies with the license terms.

You can view the requirements and supported softwares on the Item's page on Envato marketplaces. Further notes can be found in the documentation included in the package you can download after purchasing the Item.

You can find the installation instructions in the documentation file included in the package that you can download from CodeCanyon. Please note, some Items include documentation file for developers, which End-Users should not follow.

We also have update instructions in the documentation file mentioned above. You can use the auto-update feature where available, so your WP installation will notify you about new releases and you can install them with just one click. You can also download the new version from your CodeCanyon downloads page at any time free of charge, so you can manually remove the old version and install the new one. Removing the plugin won't touch of your sliders and settings on your WP installation, so you don't have to worry about losing your work. The new version will always have backwards compatibility, so your previously created contents will work the same as before.

Unfortunately, the native WP auto-update mechanism doesn't work with integrated plugins, so if you received the plugin by another purchase (e.g. WordPress themes), you won't be able to use this method. We can't send you the updates since you are not a direct client of ours and its prohibited by the licensing terms. You need to request the plugin updates from the author of your theme / template, and possibly they already released an update with a newer version.

New features will always use the new defaults, but these changes might not apply on your older works having different settings, but you can always change them with the newly introduced options.

Depending on the default settings introduced in updates, you may need to adjust some options of the new features in some cases. This should only affect the new features, your previous settings will be unchanged. Please check your settings on the plugin's admin area or read the documentation if you are using a standalone jQuery version.

We may also change some defaults for old features. It won't override the settings you used for previously created contents, but it may take effect in future works.

New versions of the plugin always have backwards compatibility and you don't have to worry about break your work. At worst case scenario, you might need to adjust some settings.

You don't have to, the plugin is fully functional without entering your Item Purchase Code. It is only needed to enable the auto-update feature, so WordPress can notify you about new releases and you can install them quickly and easily.

In the email Envato sent upon your purchase or on your CodeCanyon downloads page by clicking on the "Download" button for the corresponding item and selecting the "License Certificate" option. This will download you a text file containing your Item Purchase code.

Try to validate your Item Purchase Code later since there might be a temporary issue with our services. If the issue still persist, please contact us.

The package you have downloaded from CodeCanyon isn't the installable plugin itself, it contains other resources like the documentation, PSD files, etc. You need to unpack the ZIP file and try to upload the inside archive with the "installable" word in its name.

This message means you have one instance of the plugin already installed and activated, and you can't load a second copy. Most likely your theme already includes the plugin, thus you need to remove it first in order to use the newer version from us. In this case, please contact with the author of your theme or read our guide about removing integrated plugins in the "Advanced topics" section.

The auto-update feature in our WordPress plugins doesn't install new versions without your confirmation. You can see notifications about new updates on your Plugins and Dashboard -> Updates pages. Please note, WordPress caches the update results, so it is possible that an update won't appear instantly. Our auto-update feature requires a valid Item Purchase Code, please read the details in the documentation or the entries above.

Some 3rd party components like plugins and themes doesn't follow WordPress standards and load their own version of the jQuery library (instead of the WP built-in one) that causes problems most of the cases. In a situation like this, you should check for updates first. This issue is common in outdated plugins and themes, and there is a good chance that their authors already released updates to fix this problem. This problem can caused by any of your plugins or themes, so you should make attention to check and update every component. It is always a good practice to update everything, but you can also disable your plugins or switch themes one-by-one to find out which one causes the trouble.

If none of these are help, we have a workaround for this problem, you can enable the "Put JS includes into body" option in the Global Settings of your slider.

To maintain compatibility with new software versions and their new features, our plugins requires newer versions of the jQuery library. Usually, you can use them with jQuery 1.7, but we strongly recommend you to have at least version 1.8 or newer as some of the features of our plugins only works with those versions.

If your jQuery is up-to-date and this error message is still showing, you have to update the plugin. There was a small issue in an older version of LayerSlider that we have fixed several releases ago and updating to the latest version will fix this.

Please see our updating guide in this FAQ in the 'Installation and Updates' section. We also have a "Updating jQuery" entry under "Advanced Topics".

We are using the jQuery Transit plugin for accelerated CSS3 transitions to achieve maximum performance on all deceives and machines. As jQuery Transit doesn't support some features for 3D transforms, we needed to include a modified version. If an other plugin also uses jQuery Transit, it may overrides our version and LayerSlider will fail with this error message. In this case, you need to enable the "Put JS includes to body" option in the Global Settings of your slider. It should solve this problem, but there can be special cases when you need to remove the other version. The version of jQuery Transit that LayerSlider uses will be compatible with the original that some other plugin may want to use.

The shortcode requires at least one mandatory parameter, the ID of the slider you want to insert. This error message appears when one or more required parameter in your shortcode missing.

This error message means that the slider you are referencing for (either in a shortcode or in a PHP function) does not exists and cannot be loaded. Please verify the shortcode you entered or the ID you are using on the LayerSlider's homescreen on your WP admin area.

Please note that earlier versions of the plugin did not use fixed IDs and they may changed upon a deletion.

If you get this error message in another way, it is possible that the solution you use to insert the slider is not working properly.

Some outdated plugins and themes can cause issues in really weird ways, so you should have up-to-date versions of every plugins and themes you use. There is a really good chance that their authors already released updates to fix problems you may having.

The jQuery Validation plugin that's included in Magic Fields somehow affects the jQuery AJAX functions and caused problems with saving in LayerSlider. This issue was solved in version 4.6.1.

The issue seems to be the same as with Magic Fields, and it is fixed in version 4.6.1.

Both jQuery Transit and Isotope uses the same CSSHooks in jQuery that resulted some incompatibilities in CSS3 transitions. Since LayerSlider v4.6.0, we are using a modified jQuery Transit library to avoid issues like this.

Responsive mode is a web design approach aimed at crafting themes, plugins and other kind of web contents to provide an optimal viewing experience across a wide range of devices (from mobile phones to desktop computers). With enabled responsive mode, your sliders will adapt the layout of the viewing environment by scaling your content proportionally. 

Responsive mode will scale your content (even upwards) based on the available free space it can take. You can limit your slider maximum size with the "Max-width" option under the "Layout" tab in the Slider Settings.

As mentioned in the previous entries, responsive mode needs an initial proportion to calculate new dimensions for scaling. A full-widh slider will always be as wide as your browser window, so your slider initial size depends on the viewing environment, and the plugin cannot identify an exact proportion to work with. Another aspect is to control how scaling should work with large screens, you most likely want to enable it below a certain amount of size, and prevent any action above that. This is why we have a feature called "Responsive under". It enables you to specify imaginary borders that is dynamically enable or disable responsive layout depending on the size of your browser window.

The "Layers container" feature will create an inner area inside your sliders to have invisible borders you can position your content relative to. This area will be as wide as you specify in pixels, and will always be centered. While this feature can be used with any layout, it is made for full-width sliders. Using this feature will result a resized canvas in slider builder that has the new dimensions you have specified.

For multilingual sliders, you need a custom solution such as qTranslate or WPML. The following description deals with translating the plugin's user interface only.

• Download Poedit
• Poedit is a multiplatform application which you can use to translate .PO files easily and compile them into .MO files. You can download it from here.
  
• Start translating
  Launch Poedit and open the default .PO file (LayerSlider-en_US.po) for editing. It can be found in your "/wp-content/plugins/LayerSlider/languages/" folder. When you open this file, you will have a list of the all the available strings for translating. When you save your work, Poedit will generate an MO file, WordPress will use this file to load your translation.
  
• Use your translation
  When you finished, you need to rename your new .PO and .MO files, so WordPress will be able to identify the corresponding language that you made your work for. You have to include in their file name the name of the plugin followed by a dash and the language and country identifier separated with an underscore. Here you can find all the language codes, and here are the country identifiers. For example, your new files will be: LayerSlider-fr_FR.po and LayerSlider-fr_FR.mo.
  
  After that, you need to copy your new files into your "/wp-content/plugins/LayerSlider/languages" folder.
  
  And that's it, you are ready to go. Please note that your WordPress installation needs to be set to the exact same locale as you specified in your file names. This settings can be found in your wp-config.php file. If you are using WordPress in your native language, you don't have to worry about this setting.
  
• Publish your work
  If you translated the plugin, you can help to other users from your country. You can send us the .PO and .MO files, and we will include them in the next update of the plugin, so your translations will be available for every other users. Our email address is: contact@kreaturamedia.com

qTranslate is the most easiest way to create multilingual sliders in LayerSlider. It is a free and simple plugin that supports a shortcode-like syntax to enter text in multiple languages, so it can display the proper one for your visitors. LayerSlider supports shortcodes and other special syntaxes in the contents of layers, so you can enter something like this to create a multilingual slider:

[:en]English text[:de]German text

The line above will output “English text” if the visitor selected English page and “German text” if the visitor selected German.

You can read more about qTranslate on their homepage.

You need a "Multilingual CMS" version of WPML with installed WPML String Translation add-on.

Translating the plugin's user interface:

• Navigate WPML -> Theme and plugins localization
• Select "Translate by WPML" option in "Select how to localize the theme" section.
• In the newly appeared list of plugins, select LayerSlider and click "Scan selected plugins for strings" button.
• Under WPML -> String translation menu item, you can now see and edit the texts that LayerSlider uses.

Creating multilingual sliders:

Since version 4.6.0, we are supporting multilingual sliders as well. LayerSlider registers translatable contents in layers when you save your work. If you want to translate a previously created slider, you need to re-save it, even if you won't change anything. Once LayerSlider registered the translatable contents, they will appear under the WPML -> String translation menu item in your WP admin sidebar.

Codestyling Localization plugin can be used to translate the plugin's interface, it basically does the same thing that we described in the first entry of this section. However, it has a graphical interface to make your life easier, so you don't have to edit files and it may supports other useful tools as well.

We are using the WordPress contextual help menus (top right corner of the page) to give you a quick and easy way to access our documentation whenever you need on the plugin's pages on your WP admin interface. Also, newer versions of the plugin uses dynamic tooltips that explains the given option when you point on a setting field with your mouse cursor.

We have an entire section for this question in the Help menu on the LayerSlider's pages on your WP admin interface. Please read the "Inserting LayerSlider to your pages" section.

There are two scenario for these issues:

• There are some contents (mostly images) that cannot be loaded and the preload feature fails with the spinning circle of death:
  
  If you use images or other contents which pointing to a wrong location or cannot be loaded for some reason, the preloader will fail and your slider won't appear. You need to make sure that you don't have missing content or update them if there any. Optionally, you can disable the preload feature.
  
  
• The slider fails with a Javascript error message that most likely caused by a 3rd party component or some misconfiguration.

In both cases, you can use your browser's developer tools to verify these cases and get some useful information. These tools will indicate if the browser cannot load some contents or giving you an error message if there is anything wrong. If you can't solve the problem you are having and choose to report this issue, please include these informations if any as they can be really helpful.

LayerSlider has many settings, probably more than other slider plugins. For this matter, it needs to send and deal with more amount of data that your server may not allow in its default configuration. This is a very rare case and only affects people who using really-really lots of layers on a given slide. Please consider to split your work into different slides, but if it is not possible, you can workaround this issue with modifying your PHP settings.

You need to increase the default value of the following keys:

• max_input_vars in your php.ini
• suhosin.post.max_vars in your Suhosin config
• suhosin.request.max_vars in your Suhosin config

You can do this with the "Allow LayerSlider access to users with ..." section in the plugin's main page under your sliders list. If it's needed you can also use custom capabilities you can find here. 

Some elements like paragraphs can’t hold block-level elements and can cause issues like this. Please try to use DIVs in this case.

If you experience issues with sliders after moving your WP installation to a different server or domain, it is most likely caused by the images which URLs still pointing to your old location that may does not exists anymore. In this case, you need to enable the "Use relative URLs" option in your Global Settings that will ignore the domain name they are referencing for and will try to find your images locally.

If you have moved your WP installation folder locally (on the same server), you need to manually update the image URLs. This can be done with a search & replace action, or you can re-pick those images from your Media Library.

The export / import mechanism does not copy your images used in the slider. You need to copy them to your new uploads folder and may enable the "Use relative URLs" option in your Global Settings.

It is commonly caused by the FitVids Javascript plugin that may manipulates videos in your sliders. You need to modify the plugin call in a way to avoid applying it on the elements used in sliders. This plugin is commonly used in WordPress themes without you knowing about it, so you need to get help from the author of your theme if you experience an issue like this. Please note that we are not familiar with the themes you use and many of them uses compressed or encrypted Javascript source files, thus you should try to get help from your theme author first.

LayerSlider wants to display a preview image from your video automatically. Unfortunately, Vimeo threats Plus / Pro videos as private, even if you have allowed public access to everyone. The Vimeo API won't return any information about you Plus / Pro videos and we can't display the preview image, that's why it doesn't appear. We will solve this issue by enabling you to use custom video images.

LayerSlider wants to display a preview image from your video automatically. However, not every video has HD quality preview image, so you should try to choose a lower quality in your Global Settings of the corresponding slider.

If you are the author of the video in question, you can also upload your own preview image by editing the video on YouTube.

Some web servers uses X-HTTP headers to control restricted contents and they can causes issues like this. In your browser's developer tools you should receive a message related with this and you can check the HTTP headers that you server sends. You need to contact with your hosting provider or system administrator about how you can solve this issue.

Since version 5.0.0 Layerslider supports HTML5 self-hosted videos as well. The plugin also allows you to enter any custom HTML code or shortcodes, so you can embed any kind of content you want.  However, LayerSlider can't possible handle every video player as there is no unified way to control them, so you may have to do some adjustments with the LayerSlider API to control their playback depending on the slider events.

Most likely it is caused by an image preloader plugin or feature in your theme. You need to exclude the slider's pages or contents, or disable this plugin completely. If it is in your theme, hopefully you will find some options for this in your theme options. Either way, we can't help you in a case like this, you need to contact with the plugin's or theme's author.

Please, make sure your browser supports 3D transforms properly. We have a compatibility list in the plugin's documentation. Currently, it is supported by Chrome, Firefox, Safari and Opera 15+ on desktop. Mobile versions of Safari and Chrome also fully compatible. Internet Explorer 10 and older versions of Android Browser have some lack of support these features and they only capable to display semi-3D transitions. Older versions of Internet Explorer can display 2D transitions only.

Make sure you are using an up-to-date version of the jQuery library. For scaling and rotating, LayerSlider needs at least version 1.8 or newer.

Many themes uses the Isotope plugin that has some compatibility issues with jQuery Transit, the plugin we use for accelerated CSS3 transitions to achieve maximum performance on all devices and machines. We are already working on the solution and we will release an update as soon as possible.

Some plugins may interfering with LayerSlider in some ways and could break features like saving. We know about some of these plugins, please check the "Known 3rd party incompatibilities" section.

If you experience an issue like this, we first need to know which component causing it before we can try to figure out what's wrong. Please, try to disable every other plugins and switching to a different (potentially a default) theme. If it solves your problem, it's almost certainly caused by one of your installed plugins or themes. You can re-enable them one-by-one to find out which one causes the trouble.

Please note that in a multisite installation, you need to make attention to the network-wide activated plugins as well, because your given site may doesn't list on the installed plugins page.

It is most likely a database issue. LayerSlider may want to change its database table or get done some database related tasks when you install an update, so it is always a good idea to re-activate the plugin if you choose the FTP method. Installing updates with the auto-update mechanism doesn't require a plugin re-activation, WP does this automatically.

If you got the plugin with a theme purchase, you won't be able to re-activate integrated plugins. Some of the theme authors don't realise that this step must be a part of their implementation, so you should try to report this issue to them first.

If one of your plugins or themes is generating PHP warning or error messages, or even outputs some white spaces or line breaks, it will affect every AJAX calls that other plugins may use, including LayerSlider. In this case, you need to clear the output from these things.

Commonly, it is an issue with account permissions. Please, make sure that you have permissions to access to the LayerSlider plugin pages or the other plugins in general. You (or another administrator) can specify custom capabilities for LayerSlider to control its accessibility for other users. If you have entered an incorrect capability, it is possible that you locked out yourself. In this case, you need to reset the corresponding settings in your database.

To do that, please open phpMyAdmin (commonly accessible from your hosting provider's administration page) and select the "wp_options" table on the left site. Click "Search" and search for option_name "layerslider_custom_capability". You can remove or empty this record to restore its default state. Please note that in a WP multisite installation your table names are prefixed with the ID of your network-site.

An other explanation could be an incompatible plugin or theme. While it shouldn't be a problem, it is possible and you should try to disable them to test if it solves your problem or not.

Here is an example for a custom navigation area with the LayerSlider API. To understand this code snippet, please read the corresponding sections of the documentation in the Help menu on your WP admin interface. Please note that using the LayerSlider API requires some web development experience.

Optionally, if you just want small appearance changes, modifying a skin could be a considerably easier job.

Please read this FAQ entry carefully, fixing this issue is really easy and can be done quickly without any programming experience. The changes you need to make might seems overwhelming at the first time, but you only need to change 6 characters what you can see in the exmaple code at the bottom of this entry.

Please, verify whether your theme or another plugin are using an old version of jQuery. Old themes might hardcoding bundled versions that are no longer maintained and supported a wide range of plugins and the jQuery developers themselves. Updating your theme and plugins will likely solve issues related with jQuery, so make sure you are using the most-recent version of everything. You can make sure which component breaks your site by temporarily changing your theme or disabling plugins one-by-one until it fixes the problem.

Usually this issue are affecting themes, and the file you will need to edit is located in your /wp-content/themes//functions.php in most of the cases. If it is a plugin, the corresponding file you need to change is the PHP file with the same name that the plugin or its folder has in your /wp-content.plugins/ folder.

Once you have found the corresponding component, the easiest way is to download the theme or plugin to your desktop computer, and search in the their files for the following code: wp_deregister_script('jquery');

Your operating system has indexing feature, and you can use its search feature to avoid looking through all the files if it's not the one mentioned above. You will only need to do these 3 easy steps when you have found the "wp_deregister_script('jquery');" line:

• Prepend a double slash (//) at the beginning of the "wp_deregister_script('jquery');" line.
• Also prepend a double slash at the beginning of the line "wp_register_script('jquery') line if any.
• Finally, prepend a double slash at the beginning of the line that starts with the following: wp_enqueue_script('jquery' ...

These function names mentioned above are common, and widely used to include web resources, thus you need to make sure you are making these changes with the ones that have the jquery keyword as their first parameter.

You can make these changes with the built-in theme or plugin editors. You can find those under the Appearance -> Editor or Plugins -> Editor pages. If anything goes wrong, you can always revert your changes via FTP. Also, you can override the edited file with the theme's original if you don't know what to do.

The following example demonstrates the changes you need to do, but the code will likely differing a little what you have in your theme. With that reason, we are using placeholders for URLs and version numbers.

The following example lines:

 wp_deregister_script('jquery');
 wp_register_script('jquery'); (your theme may not contain this line)
 wp_enqueue_script('jquery', , array(), );

Should be like this:

 //wp_deregister_script('jquery');
 //wp_register_script('jquery');
 //wp_enqueue_script('jquery', , array(), );

As of 9th September 2013, Envato obligates ThemeForest authors to include 3rd party plugins as stand-alone items in their work. The new method enables to install additional components optionally, and they can be removed/disabled in the old fashioned WordPress way. The most-recent version of your WordPress theme will most likely contain these changes, and disabling bundled plugins will no longer be a problem.

This section is only intended to show you the most recent changes. If you interested the plugin's complete development history, please read the documentation file that you can find in the downloaded package from CodeCanyon.