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":{"icon.svg":{"filename":"icon.svg","revision":2631785,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":2631785,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":2631785,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is stored in the \/assets directory.","2":"This is the second screen shot"}},"plugin_section":[],"plugin_tags":[14081,13827,25846,286,4140],"plugin_category":[45],"plugin_contributors":[],"plugin_business_model":[],"class_list":["post-142186","plugin","type-plugin","status-publish","hentry","plugin_tags-area","plugin_tags-delivery","plugin_tags-polygons","plugin_tags-woocommerce","plugin_tags-zone","plugin_category-ecommerce","plugin_committers-arnaudpf"],"banners":{"banner":"https:\/\/ps.w.org\/delivery-area-free-for-woocommerce\/assets\/banner-772x250.png?rev=2631785","banner_2x":"https:\/\/ps.w.org\/delivery-area-free-for-woocommerce\/assets\/banner-1544x500.png?rev=2631785","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/delivery-area-free-for-woocommerce\/assets\/icon.svg?rev=2631785","icon":"https:\/\/ps.w.org\/delivery-area-free-for-woocommerce\/assets\/icon.svg?rev=2631785","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\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 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 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\nA brief Markdown Example<\/h3>\n\n
\n
\n
\n
<?php code(); \/\/ goes in backticks ?>\n<\/code><\/pre>\n\n\n\n
A question that someone might have<\/h3><\/dt>\n
What about foo bar?<\/h3><\/dt>\n
1.0<\/h4>\n\n
\n
0.5<\/h4>\n\n
\n