Edit File by line

=== Plugin Name ===

[0] Fix | Delete

Contributors: (this should be a list of wordpress.org userid's)

[1] Fix | Delete

Donate link: https://themify.me/

[2] Fix | Delete

Tags: comments, spam

[3] Fix | Delete

Requires at least: 5.3

[4] Fix | Delete

Tested up to: 3.4

[5] Fix | Delete

Stable tag: 4.3

[6] Fix | Delete

License: GPLv2 or later

[7] Fix | Delete

License URI: http://www.gnu.org/licenses/gpl-2.0.html

[8] Fix | Delete

[9] Fix | Delete

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

[10] Fix | Delete

[11] Fix | Delete

== Description ==

[12] Fix | Delete

[13] Fix | Delete

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

[14] Fix | Delete

[15] Fix | Delete

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

[16] Fix | Delete

Markdown parsed.

[17] Fix | Delete

[18] Fix | Delete

A few notes about the sections above:

[19] Fix | Delete

[20] Fix | Delete

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

[21] Fix | Delete

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

[22] Fix | Delete

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

[23] Fix | Delete

* "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on

[24] Fix | Delete

higher versions... this is just the highest one you've verified.

[25] Fix | Delete

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

[26] Fix | Delete

stable.

[27] Fix | Delete

[28] Fix | Delete

Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so

[29] Fix | Delete

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

[30] Fix | Delete

for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt`

[31] Fix | Delete

is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in

[32] Fix | Delete

your in-development version, without having that information incorrectly disclosed about the current stable version

[33] Fix | Delete

that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.

[34] Fix | Delete

[35] Fix | Delete

If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where

[36] Fix | Delete

you put the stable version, in order to eliminate any doubt.

[37] Fix | Delete

[38] Fix | Delete

== Installation ==

[39] Fix | Delete

[40] Fix | Delete

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

[41] Fix | Delete

[42] Fix | Delete

e.g.

[43] Fix | Delete

[44] Fix | Delete

1. Upload `tbp.php` to the `/wp-content/plugins/` directory

[45] Fix | Delete

1. Activate the plugin through the 'Plugins' menu in WordPress

[46] Fix | Delete

1. Place `<?php do_action('plugin_name_hook'); ?>` in your templates

[47] Fix | Delete

[48] Fix | Delete

== Frequently Asked Questions ==

[49] Fix | Delete

[50] Fix | Delete

= A question that someone might have =

[51] Fix | Delete

[52] Fix | Delete

An answer to that question.

[53] Fix | Delete

[54] Fix | Delete

= What about foo bar? =

[55] Fix | Delete

[56] Fix | Delete

Answer to foo bar dilemma.

[57] Fix | Delete

[58] Fix | Delete

== Screenshots ==

[59] Fix | Delete

[60] Fix | Delete

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from

[61] Fix | Delete

the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets

[62] Fix | Delete

directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`

[63] Fix | Delete

(or jpg, jpeg, gif).

[64] Fix | Delete

2. This is the second screen shot

[65] Fix | Delete

[66] Fix | Delete

== Changelog ==

[67] Fix | Delete

[68] Fix | Delete

= 1.0 =

[69] Fix | Delete

* A change since the previous version.

[70] Fix | Delete

* Another change.

[71] Fix | Delete

[72] Fix | Delete

= 0.5 =

[73] Fix | Delete

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

[74] Fix | Delete

[75] Fix | Delete

== Upgrade Notice ==

[76] Fix | Delete

[77] Fix | Delete

= 1.0 =

[78] Fix | Delete

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

[79] Fix | Delete

[80] Fix | Delete

= 0.5 =

[81] Fix | Delete

This version fixes a security related bug. Upgrade immediately.

[82] Fix | Delete

[83] Fix | Delete

== Arbitrary section ==

[84] Fix | Delete

[85] Fix | Delete

You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated

[86] Fix | Delete

plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or

[87] Fix | Delete

"installation." Arbitrary sections will be shown below the built-in sections outlined above.

[88] Fix | Delete

[89] Fix | Delete

== A brief Markdown Example ==

[90] Fix | Delete

[91] Fix | Delete

Ordered list:

[92] Fix | Delete

[93] Fix | Delete

1. Some feature

[94] Fix | Delete

1. Another feature

[95] Fix | Delete

1. Something else about the plugin

[96] Fix | Delete

[97] Fix | Delete

Unordered list:

[98] Fix | Delete

[99] Fix | Delete

* something

[100] Fix | Delete

* something else

[101] Fix | Delete

* third thing

[102] Fix | Delete

[103] Fix | Delete

Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].

[104] Fix | Delete

Titles are optional, naturally.

[105] Fix | Delete

[106] Fix | Delete

[markdown syntax]: http://daringfireball.net/projects/markdown/syntax

[107] Fix | Delete

"Markdown is what the parser uses to process much of the readme file"

[108] Fix | Delete

[109] Fix | Delete

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

[110] Fix | Delete

> Asterisks for *emphasis*. Double it up for **strong**.

[111] Fix | Delete

[112] Fix | Delete

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

[113] Fix | Delete