Simple answer: add_shortcode( ‘hidemytext’, ‘__return_false’ ); But shortcodes should never be used like that. Imagine what happens when the plugin or theme with that shortcode is turned off: everyone can see the content now. This is not very user friendly. So switch the logic: show nothing or the bare shortcode tag by default, show the … Read more
Method #1 If available, I would use the: shortcode_atts_{$shortcode} filter to collect the attributes of a given shortcode. Example: $text=” “; $out = wpse172275_get_all_attributes( ‘gallery’, $text ); print_r( $out ); with the output: Array ( [0] => [1] => Array ( [ids] => 1,2 https://wordpress.stackexchange.com/questions/172275/extract-attribute-values-from-every-shortcode-in-post => file ) [2] => Array ( [ids] => 3 … Read more
Is it Ok? Yes! Is it Optimal? No What Would Be Better? Shortcodes map on to PHP functions, so why not cut out the middle man and go straight to the original function? Are there any other downsides? Yes! That shortcode had to come from somewhere, now you have a dependency, maybe the plugin that … Read more
Shortcodes are a WordPress thing, hence not being in the PHP manual. What you do want to look at in the PHP manual is the section on callbacks. add_shortcode() accepts a shortcode name, and a callback. In that section of the PHP manual you can see the 3 main types of callbacks: // Type 1: … Read more
Since WooCommerce 3.2, Woocommerce shortcodes and their available attributes have changed. So try the following shortcode instead (for “foo” product category): [product_category limit=”90″ columns=”3″ category=”foo” paginate=”true”] or inside php code: echo do_shortcode( ‘[product_category limit=”90″ columns=”3″ category=”foo” paginate=”true”]’ ); Now you will see that the sorting options dropdown appear. Note: orderby argument with an empty value … Read more
Lets look at the shortcode [SH_TEST var1=”somevalue” var2=”someothervalue”]THE SHORTCODE CONTENT[/SH_TEST] the shortcode handler function accepts 3 paramters $atts – an array of attributes passed by the shortcode in our case: $atts[‘var1’] is set to ‘somevalue’ $atts[‘var2’] is set to ‘someothervalue’ $content – is a string of the value enclosed with in the shortcode tags, in … Read more
Use this instead of the line in wich you define $days (your second line): $transient = get_transient( ‘your_transient_key’ ); if( !$transient ): $days = file_get_contents( ‘json_file’ ); set_transient( ‘your_transient_key’, $days, DAY_IN_SECONDS*7 ); else: $days = $transient; endif; $days = json_decode( $days ); … May be a bit rough but you get the idea.
By popular demand: The solution is simply to replace print to return . Shortcodes should always return the value instead of printing or echoing it out.
Normally WordPress does not run shortcode that you put into a custom field. By default, Custom Fields display whatever value you enter, as plain-text, so if you try entering a shortcode, (in the format [shortcode] VALUE [/shortcode]) you’ll end up displaying the entire text, including the tags. Add the following in your template file, it … Read more
WordPress interpreted your shortcode like this: The main issue being, that you have a unclosed shortcode of the same tag in front of an enclosing shortcode of the same tag, which won’t be parsed correctly. The documentation states that you might run into problems with unclosed shortcodes. When you call your shortcode like this: [span … Read more