Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga asistencia ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

WP Battle by Alex Lundin

Descripción

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.

Arbitrary section

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

Ordered list:

  1. Some feature
  2. Another feature
  3. Something else about the plugin

Unordered list:

  • something
  • 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 ?>

Bloques

Este plugin provee 1 bloque.

  • WP Battle by Alex Lundin

Instalación

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

e.g.

  1. Upload asl-battle.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

Preguntas frecuentes

A question that someone might have

An answer to that question.

What about foo bar?

Answer to foo bar dilemma.

Reseñas

No hay reseñas para este plugin.

Colaboradores y desarrolladores

“WP Battle by Alex Lundin” es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

Traduce “WP Battle by Alex Lundin” a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN , o suscríbete al log de desarrollo por RSS .

Registro de cambios

1.0

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

0.5

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