Upgrade notices describe the reason a user should upgrade. No more than 300 characters.<\/p>","5.0":"
Upgrade to Version 5.0 for major nothingness. Nothing has changed.<\/p>"},"ratings":{"1":3,"2":0,"3":1,"4":1,"5":7},"assets_icons":{"icon.svg":{"filename":"icon.svg","revision":2412921,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"BANNER-772\u00d7250.PNG":{"filename":"BANNER-772\u00d7250.PNG","revision":2404372,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3434838,"resolution":false,"location":"assets","locale":"","contents":"{\"landingPage\":\"\\\/wp-admin\\\/\",\"phpExtensionBundles\":[\"kitchen-sink\"],\"features\":{\"networking\":true},\"steps\":[{\"step\":\"installPlugin\",\"options\":{\"activate\":true},\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"test-plugin-3\"}},{\"step\":\"login\",\"username\":\"admin\",\"password\":\"password\"}]}"}},"all_blocks":{"namespace\/block-name":{"name":"namespace\/block-name","title":"Namespace Block Name"},"should-match\/block-name":{"name":"should-match\/block-name","title":"Title here"},"my-plugin\/book-with-title":{"name":"my-plugin\/book-with-title","title":"Title here"},"my-plugin\/book-with-title-after-args":{"name":"my-plugin\/book-with-title-after-args","title":"Title here"}},"tagged_versions":["0.point-release","5.0","5.0.1","5.0.10","5.0.11","5.0.12","5.0.2","5.0.3","5.0.4","5.0.6","5.0.9","6.0.0","8.0","9.0","9.1","9.1.1","9.1.2","9.1.3","9.1.4","9.1.5","9.1.6","empty-tag","tag-is-ok-2","tag-is-ok-3","tag-is-ok-4","tag-no-files-2","tag-no-readme","tag-of-tags-2","tag1","test-tag","v1","v2","v3","v3.1","v3.2","v4","v4.1","v4.2","v4.3","v4.4","v4.5","v4.5.1","v4.5.2","v6.0-a1"],"block_files":["\/tags\/9.1.5\/blocks.js"],"assets_screenshots":{"Screenshot-2.PNG":{"filename":"Screenshot-2.PNG","revision":2404363,"resolution":"2","location":"assets","locale":""},"screenshot-1-ary.png":{"filename":"screenshot-1-ary.png","revision":2064776,"resolution":"1","location":"assets","locale":"ary"},"screenshot-1-de_CH.png":{"filename":"screenshot-1-de_CH.png","revision":2079638,"resolution":"1","location":"assets","locale":"de_CH"},"screenshot-1-de_DE.png":{"filename":"screenshot-1-de_DE.png","revision":2064776,"resolution":"1","location":"assets","locale":"de_DE"},"screenshot-1.png":{"filename":"screenshot-1.png","revision":2064776,"resolution":"1","location":"assets","locale":""}},"screenshots":{"1":"This screenshot description corresponds to a potentially localised screenshot in the \/assets\/ directory."},"jetpack_post_was_ever_published":false},"plugin_section":[172757,163309],"plugin_tags":[125832],"plugin_category":[],"plugin_contributors":[125833,77591],"plugin_business_model":[],"class_list":["post-87","plugin","type-plugin","status-disabled","hentry","plugin_section-block","plugin_section-blocks","plugin_tags-test-plugins","plugin_contributors-dd128","plugin_contributors-dd32","plugin_committers-dd128","plugin_committers-dd32","plugin_support_reps-dd256","plugin_support_reps-dd64"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/test-plugin-3\/assets\/icon.svg?rev=2412921","icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/test-plugin-3_b8ced8.svg","icon_2x":false,"generated":true},"screenshots":[{"src":"https:\/\/ps.w.org\/test-plugin-3\/assets\/screenshot-1.png?rev=2064776","caption":"This screenshot description corresponds to a potentially localised screenshot in the \/assets\/ directory."},{"src":"https:\/\/ps.w.org\/test-plugin-3\/assets\/Screenshot-2.PNG?rev=2404363","caption":""}],"raw_content":"\n
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.<\/p>\n\n
This is the long description. No limit, and you can use Markdown (as well as in the following sections).<\/p>\n\n
For backwards compatibility, if this section is missing, the full length of the short description will be used, and\nMarkdown parsed.<\/p>\n\n
A few notes about the sections above:<\/p>\n\n
Stable tag should indicate the Subversion \"tag\" of the latest stable version, or \"trunk,\" if you use Note that the If no stable tag is provided, it is assumed that trunk is stable, but you should specify \"trunk\" if that's where\nyou put the stable version, in order to eliminate any doubt.<\/p><\/li>\n<\/ul>\n\n Testing out some Markdown bugs:\nExamples:\n define( 'TC_PRE', 'Theme Review:[[br]]\n - Themes should be reviewed using \"define(\\'WP_DEBUG\\', true);\" in wp-config.php[[br]]\n - Themes should be reviewed using the test data from the Theme Checklists (TC)\n -----\n ' );<\/p>\n\n three backtics:\n or indents\n add_action( 'init', function() {\n \/\/ do stuff\n } );<\/p>\n\n You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated\nplugins where more information needs to be conveyed that doesn't fit into the categories of \"description\" or\n\"installation.\" Arbitrary sections will be shown below the built-in sections outlined above.<\/p>\n\n Ordered list:<\/p>\n\n Unordered list:<\/p>\n\n Here's a link to WordPress<\/a> and one to Markdown's Syntax Documentation<\/a>.\nTitles are optional, naturally.<\/p>\n\n Markdown uses email style notation for blockquotes and I've been told:<\/p>\n\n Asterisks for emphasis<\/em>. Double it up for strong<\/strong>.<\/p>\n<\/blockquote>\n\n This section describes how to install the plugin and get it working.<\/p>\n\n e.g.<\/p>\n\n An answer to that question.<\/p><\/dd>\n Answer to foo bar dilemma.<\/p><\/dd>\n `body, h1, p {\n color: #f1f1f1 !important;\n}<\/p><\/dd>\n background-color: #5f5f5f !important;\n}`<\/p><\/dd>\n\/trunk\/<\/code> for\nstable.<\/p>\n\nreadme.txt<\/code> of the stable tag is the one that is considered the defining one for the plugin, so\nif the \/trunk\/readme.txt<\/code> file says that the stable tag is 4.3<\/code>, then it is \/tags\/4.3\/readme.txt<\/code> that'll be used\nfor displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt<\/code>\nis the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt<\/code> to reflect changes in\nyour in-development version, without having that information incorrectly disclosed about the current stable version\nthat lacks those changes -- as long as the trunk's readme.txt<\/code> points to the correct stable tag.<\/p>\n\ndefine( 'TC_POST', 'Feel free to make use of the contact details below if you have any questions,\ncomments, or feedback:[[br]]\n[[br]]\n* Leave a comment on this ticket[[br]]\n* Send an email to the Theme Review email list[[br]]\n* Use the #wordpress-themes IRC channel on Freenode.' );\n<\/code><\/pre>\n\nadd_action( 'init', function() {\n \/\/ do stuff\n} );<\/code><\/p>\n\nArbitrary section<\/h3>\n\n
A brief Markdown Example<\/h3>\n\n
\n
\n
\n
<?php code(); \/\/ goes in backticks ?>\n<\/code><\/pre>\n\n\n\n
plugin-name.php<\/code> to the \/wp-content\/plugins\/<\/code> directory<\/li>\n<?php do_action('plugin_name_hook'); ?><\/code> in your templates<\/li>\n<\/ol>\n\n\n\n
A question that someone might have<\/h3><\/dt>\n
What about foo bar?<\/h3><\/dt>\n
Markdown 1<\/h3><\/dt>\n
wpwrap {<\/h3><\/dt>\n
Markdown 2<\/h3><\/dt>\n
background-color: #5f5f5f !important;\n}\nbody, h1, p {\n color: #f1f1f1 !important;\n}\n<\/code><\/pre><\/dd>\n\n<\/dl>\n\n\n1.0<\/h3>\n\n
\n