Maintenance version; upgraded plugin to new version of WP_PluginBase to prevent class name clashes during future upgrades.<\/p>","1.0.1":"
Fixed a bug where WP_PluginBase is properly included and defined. This is the 2nd. version of WP Shortcode Shield.<\/p>","1.0":"
This plugin allows you to refer to a WordPress shortcode within the content of posts and pages without that shortcode being automagically expanded by WordPress. The plugin takes advantage of the fact that the WordPress ShortCode API<\/a> does not support nested shortcodes to allow this plugin's shortcode to wrap the shortcode being documented.<\/p>\n\n The shortcode parser uses a single pass on the post content. This means that if \n the $content parameter of a shortcode handler contains another shortcode, it won't\n be parsed<\/p>\n<\/blockquote>\n\n The plugin supports both the self closing If using the self-closing form of the shortcode, you need to supply the name of the shortcode you are documenting using the ... WordPress will use the ']' character inside the ... will display [another-shortcode-name]<\/em> in your post's of page's content.<\/p>\n\n If you are using the enclosing form of the shortcode, you can either supply the shortcode to be documented with or without enclosing '[' and ']' characters; if they are omitted, the plugin will add them for you, so that usage such as<\/p>\n\n ... and<\/p>\n\n ... will display the same results, namely [another-shortcode-name]<\/em>.<\/p>\n\n Finally a note of caution, you cannot mix the enclosing and self closing form of the plugin's shortcode within the same post or page; this is not a limitation of the plugin, but the way in which WordPress implements the ShortCode API<\/a> ...<\/p>\n\n The parser does not handle mixing of enclosing and non-enclosing forms of the same\n shortcode as you would want it to. For example, if you have:<\/p>\n \n Instead of being treated as two shortcodes separated by the text \" non-enclosed content \",\n the parser treats this as a single shortcode enclosing \" non-enclosed content [myshortcode]\n enclosed content\".<\/p>\n<\/blockquote>\n\n\n In short, very easily. But before you read any further, take a look at Asking For WordPress Plugin Help And Support Without Tears<\/a> before firing off a question. In order of preference, you can ask a question on the WordPress support forum<\/a>; this is by far the best way so that other users can follow the conversation. You can ask me a question on Twitter; I'm @vicchi<\/a>. Or you can drop me an email instead. I can't promise to answer your question but I do promise to answer and do my best to help.<\/p><\/dd>\n Absolutely. Go to the WP Shortcode Shield home page<\/a> for the latest information. There's also the official WordPress plugin repository page<\/a> and the source for the plugin is on GitHub<\/a> as well.<\/p><\/dd>\n Totally; this plugin is licensed under the GNU General Public License v2 (GPLV2). See http:\/\/www.gnu.org\/licenses\/old-licenses\/gpl-2.0.txt for the full license terms.<\/p><\/dd>\n\n<\/dl>\n\n\n The current version is 1.1.0 (2012.11.12)<\/p>\n\n\n
[shortcode]<\/code> and enclosing [shortcode]content[\/shortcode]<\/code> forms and supports a short form name of the shortcode, [wp_scs]<\/code> as well as the more verbose [wp_shortcode_shield]<\/code> form. For the sake of brevity, the remainder of this documentation will use the [wp_scs]<\/code> short form name.<\/p>\n\ncode<\/code> attribute but without using the enclosing [<\/code> and ]<\/code> characters. This is because when parsing shortcodes, WordPress looks for the first occurrence of the ']' character to terminate the shortcode. As a result of this, usage such as<\/p>\n\n[wp_scs code=\"[another-shortcode-name]\"]\n<\/code><\/pre>\n\ncode<\/code> attribute to try and terminate the shortcode name, which is not what is desired. Instead, the plugin automagically adds the terminating '[' and ']' characters to the plugin's output, so that usage such as<\/p>\n\n[wp_scs code=\"another-shortcode-name\"]\n<\/code><\/pre>\n\n[wp_scs][another-shortcode-name][\/wp_scs]\n<\/code><\/pre>\n\n[wp_scs]another-shortcode-name[\/wp_scs]\n<\/code><\/pre>\n\n\n
[myshortcode example='non-enclosing' \/] non-enclosed content [myshortcode] enclosed content\n [\/myshortcode]<\/code><\/p>\n \n \n
wp-shortcode-shield<\/code> folder to the wp-content\/plugins<\/code> folder on your web server.<\/li>\n\n
1.1.0<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0<\/h4>\n\n
\n