documentgt

Download Documentgt

If you can't read please download the document

Upload: aditi

Post on 16-Jan-2016

1 views

Category:

Documents


0 download

DESCRIPTION

fgsdgdg

TRANSCRIPT

=== Plugin Name ===Contributors (this should be a list of wordpress.org userid's)Donate link httpexample.comTags comments, spamRequires at least 3.0.1Tested up to 3.4Stable tag 4.3License GPLv2 or laterLicense URI httpwww.gnu.orglicensesgpl-2.0.htmlHere 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, andMarkdown parsed.A few notes about the sections above Contributors is a comma separated list of wp.orgwp-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 onhigher 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` forstable. Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, soif the `trunkreadme.txt` file says that the stable tag is `4.3`, then it is `tags4.3readme.txt` that'll be usedfor 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 inyour in-development version, without having that information incorrectly disclosed about the current stable versionthat 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 whereyou 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-contentplugins` directory1. Activate the plugin through the 'Plugins' menu in WordPress1. Place `php do_action('plugin_name_hook'); ` in your templates== Frequently Asked Questions === A question that someone might have =An answer to that question.= What about foo bar =Answer to foo bar dilemma.== Screenshots ==1. This screen shot description corresponds to screenshot-1.(pngjpgjpeggif). Note that the screenshot is taken fromthe assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the assets directory take precedence. For example, `assetsscreenshot-1.png` would win over `tags4.3screenshot-1.png` (or jpg, jpeg, gif).