Upgrade notices describe the reason a user should upgrade. No more than 300 characters.<\/p>","0.5":"
This version fixes a security related bug. Upgrade immediately.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":"2181224","resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":[],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"This screen shot description corresponds","2":"This is the second screen shot"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[25744,455,2479],"plugin_category":[44,54],"plugin_contributors":[177542],"plugin_business_model":[],"class_list":["post-111411","plugin","type-plugin","status-publish","hentry","plugin_tags-email-subscriber","plugin_tags-newsletter","plugin_tags-subscriber","plugin_category-discussion-and-community","plugin_category-security-and-spam-protection","plugin_contributors-awesomecoders","plugin_committers-awesomecoders"],"banners":{"banner":"https:\/\/ps.w.org\/awesome-newsletter\/assets\/banner-772x250.png?rev=2181224","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/awesome-newsletter_ff5757.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Use shortcode ( [newsletter_form] ) to show the subscriber form<\/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 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\n<\/dl>\n\n\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\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
\/wp-content\/plugins\/plugin-name<\/code> directory, or install the plugin through the WordPress plugins screen directly.<\/li>\n\n
1.0<\/h4>\n\n
\n
0.5<\/h4>\n\n
\n