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
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
Note that the
readme.txtof the stable tag is the one that is considered the defining one for the plugin, so
/trunk/readme.txtfile says that the stable tag is
4.3, then it is
/tags/4.3/readme.txtthat’ll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk
readme.txtto 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.txtpoints 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.
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
A brief Markdown Example
- Some feature
- Another feature
- Something else about the plugin
- something else
- third thing
Here’s a link to WordPress 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 ?>
Este plugin disponibiliza 1 bloco.
- WP Battle by Alex Lundin
This section describes how to install the plugin and get it working.
- Activate the plugin through the ‘Plugins’ menu in WordPress
<?php do_action('plugin_name_hook'); ?>in your templates
A question that someone might have
An answer to that question.
What about foo bar?
Answer to foo bar dilemma.
Não existem avaliações para esse plugin.
Colaboradores e desenvolvedores
“WP Battle by Alex Lundin” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.Colaboradores
Traduzir “WP Battle by Alex Lundin” para o seu idioma.
Interessado no desenvolvimento?
Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.
Registro de alterações
- A change since the previous version.
- Another change.
- List versions from most recent at top to oldest at bottom.