Lightning Advanced Slider archived

=== Lightning Advanced Slider === Contributors: kurudrive Donate link: https://lightning.nagoya/ja/ Tags: slider Requires at least: 5.3 Tested up to: 5.7 Stable tag: 0.6.3 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html

Here is a short description of the plugin. This should be no more than 150 characters. No markup here.

== Description ==

This is the long description. No limit, and you can use Markdown (as well as in the following sections).

For backwards compatibility, if this section is missing, the full length of the short description will be used, and Markdown parsed.

A few notes about the sections above:

• "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames

• "Tags" is a comma separated list of tags that apply to the plugin

• "Requires at least" is the lowest version that the plugin will work on

• "Tested up to" is the highest version that you've successfully used to test the plugin. Note that it might work on higher versions... this is just the highest one you've verified.

• Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use /trunk/ for stable.

  Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that'll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes -- as long as the trunk's readme.txt points to the correct stable tag.

  If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where you put the stable version, in order to eliminate any doubt.

== Installation ==

This section describes how to install the plugin and get it working.

e.g.

1. Upload plugin-name.php to the /wp-content/plugins/ directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. Place <?php do_action('plugin_name_hook'); ?> in your templates

== Changelog ==

= 0.6.3 = [ Bugfix ] Delete debug code

= 0.6.2 = [ Specification change ] Add deprecated message.

= 0.6.1 = [ Bugfix ] Fix PHP error on using VK Blocks Pro.

= 0.6.0 = Cope with hide slide Lightning 9.11.0 / Lightning Pro 4.11.0

= 0.5.1 = Update checker version up

= 0.5.0 = [ Specification change ] Cope with header transmission

= 0.4.1 = [ Bugfix ] Change to Lightning only

= 0.3.1 = [ Bugfix ] LP template

= 0.3.0 = [ Add function ] Add transition time setting. [ Bugfix ] IE11

= 0.2.1 = [ Bugfix ] When slide count is only one that kill loop function.

= 0.2.0 = [ Add function ] Can use short cord