Test Plugin 3


This is the TRUNK readme as of 5.0.6.

Howdy, this is a testing comment. Color should be colour, login and logins should flag, as well as personalized and urls.

For best README.md support, the fields under the plugin title, Contributors.. Tags.. etc, should be in a similar format to this readme example. This means that there should be no characters after the : other than the value, no formatting, just a value and new line.

Esta es la descripción larga. No hay límite y puedes usar Markdown (así como en las siguientes secciones).

Para tener compatibilidad hacia atrás, si falta esta sección, se usará la longitud completa de la descripción corta, y
se analizará el Markdown.

Algunas notas sobre las secciones anteriores:

  • «Contributors» es una lista separada por comas de nombres de usuario de wp.org o wp-plugins.org
  • «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

    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.

Testing out some Markdown bugs:
define( ‘TC_PRE’, ‘Theme Review:[[br]]
– Themes should be reviewed using «define(\’WP_DEBUG\’, true);» in wp-config.php[[br]]
– Themes should be reviewed using the test data from the Theme Checklists (TC)
‘ );

define( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions,
comments, or feedback:[[br]]
* Leave a comment on this ticket[[br]]
* Send an email to the Theme Review email list[[br]]
* Use the #wordpress-themes IRC channel on Freenode.' );

three backtics:
add_action( 'init', function() {
// do stuff
} );

or indents
add_action( ‘init’, function() {
// do stuff
} );

Sección arbitraria

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.

Un breve ejemplo de Markdown

Lista ordenada:

  1. Una característica
  2. Otra característica
  3. Algo más sobre el plugin

Lista desordenada:

  • algo
  • algo más
  • una tercera cosa

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


  • This screenshot description corresponds to a potentially localised screenshot in the /assets/ directory.


Este plugin proporciona 4 bloques.

  • Title here
  • Title here
  • Namespace Block Name
  • Title here


Esta sección describe cómo instalar el plugin y hacer que funcione.

p. ej.

  1. Sube el archivo plugin-name.php al directorio /wp-content/plugins/
  2. Activa el plugin desde el menú «Plugins» de WordPress
  3. Place <?php do_action('plugin_name_hook'); ?> in your templates

Preguntas frecuentes

Una pregunta que alguien podría tener

Una respuesta a esa pregunta.

¿Qué pasa con «foo bar»?

Respuesta al dilema de «foo bar».

Markdown 1

`body, h1, p {
color: #f1f1f1 !important;

wpwrap {

background-color: #5f5f5f !important;

Markdown 2

wpwrap {

    background-color: #5f5f5f !important;
body, h1, p {
    color: #f1f1f1 !important;


8 de septiembre de 2016 1 respuesta
Apart from the incorrect form title this is one amazing plugin for this reason I’m only giving it 4 stars 😉 Edit: I’ve removed another star marking this review down to 3 stars, I came here to edit the version of WordPress I’m using, 4.6.1 is not correct, I’m using /trunk but I cannot change from 4.6.1 to the original optional version that was available when first submitting a review. Edit2: I’ve removed another star this time because when I submitted my original review I checked the checkbox «Notify me of follow-up replies via email» but looking to the left in the sidebar I see that I am not subscribed this review. During this edit I have the option to once again select the checkbox «Notify me of follow-up replies via email» which I will now check before hitting submit. Edit3: I am still not subscribed, I’ve also removed another star because in the sidebar to the left is «Topic Info» it should read «Review Info», also «Topic Tags» should be «Review Tags» Edit4: I cannot remove any more stars, i.e. I cannot change this to 0 stars, this is a good thing, adding a star back to make this 2 stars again 🙂 Edit5: Removed that star as when not logged in underneath my review I see «You must be logged in to reply to this topic.», this should read «You must be logged in to reply to this review.» Edit6: Changing my review back to 5 stars because all this is, bugs and all is still AWESOME 🙂
Leer todas las 11 reseñas

Colaboradores y desarrolladores

«Test Plugin 3» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


«Test Plugin 3» ha sido traducido a 8 idiomas locales. Gracias a los traductores por sus contribuciones.

Traduce «Test Plugin 3» a tu idioma.

¿Interesado en el desarrollo?

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

Registro de cambios


  • Un cambio desde la versión anterior.
  • Otro cambio.
  • Otro cambio que esta vez significa algo.
  • Una línea de registro de cambios para probar https://meta.trac.wordpress.org/changeset/8412