/WP-Plugin-Custom-Code

Separate text areas for adding single-use CSS and JavaScript. No more JavaScript inside of the WYSIWYG editor! - :thumbsup:

Primary LanguagePHP

WP-Plugin-Custom-Code

Contributors: (should be a list of wordpress.org userid's) Donate link: http://example.com/ Tags: custom CSS, custom JavaScript Requires at least: Tested up to: Stable tag: License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html

Provides separate text areas for adding single-use CSS and JavaScript. No more JavaScript inside of the WYSIWYG editor!

== Description ==

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 ==

The usual steps apply...

  1. Upload lss-custom-code 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

== Frequently Asked Questions ==

= Question 1 =

The answer

== Screenshots ==

  1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets directory take precedence. For example, /assets/screenshot-1.png would win over /tags/4.3/screenshot-1.png (or jpg, jpeg, gif).
  2. This is the second screen shot

== Changelog ==

= 1.0 =

  • A change since the previous version.
  • Another change.

= 0.5 =

  • List versions from most recent at top to oldest at bottom.

== Upgrade Notice ==

= 1.0 = Upgrade notices describe the reason a user should upgrade. No more than 300 characters.

= 0.5 = This version fixes a security related bug. Upgrade immediately.

== Markdown ==

Here's a link to Markdown and one to Markdown's Syntax Documentation. Titles are optional, naturally.

Markdown uses email style notation for blockquotes and I've been told:

Asterisks for emphasis. Double it up for strong.

<?php code(); // goes in backticks ?>