This is basic function to create a shortcodes. Put this code in your functions.php function smile_shortcode() { $output = get_template_directory_uri() . ‘/images/smile.png’; // put your smile image here $_image=”<img src=”” . $output . ‘”>’; return $_image; } add_shortcode(‘smile’,’smile_shortcode’); Then go to your dashboard and post editor. Remember to put [smile] in your post. More: http://codex.wordpress.org/Function_Reference/add_shortcode
The below WordPress snippet will give you a list of all the WordPress shortcodes you have available on your blog. <?php global $shortcode_tags; echo ‘<pre>’; print_r($shortcode_tags); echo ‘</pre>’; ?> Also check the Codex for more information about shortcodes
To get the URL for lost password use wp_lostpassword_url() Reference: wp_lostpassword_url()
If building a multipurposetheme (Hello Themeforest!), I would always use a Custom Post Type for something like this. The reason is, as you already mentioned in your shortcode approach, you have too many fields and variables even in the beginning. Then, to have your Theme serve as many customers as possible, you have to add … Read more
For anyone that comes across this in the future, here is what I figured out: $askavl_instagram_contact_title = get_post_meta(get_the_ID(), ‘askavl_instagram_contact_title’, true); if(isset($askavl_instagram_contact_title) && $askavl_instagram_contact_title != “”) : $tag = str_replace(“#”,””, ((string)$askavl_instagram_contact_title) ); $thumbsize = “220px”; $image_limit = “2”; $easyInstagramSC = “[easy-instagram limit={$image_limit} caption_hashtags=false caption_char_limit=0 author_text=”” thumb_click=’thickbox’ time_text=”” thumb_size={$thumbsize} tag='{$tag}’]”; echo do_shortcode( $easyInstagramSC ); From what I … Read more
after_setup_theme should not execute after the shortcodes process. Shortcodes process when the post body renders. after_setup_theme runs well before that. Your analysis of the problem is incorrect. This looks like a variable scope problem to me. None of the variables inside your custom_login function are going to be accessible outside that function. Their “scope” is … Read more
I’m not quite sure this is what you are trying to do, however, this is one way to use an external template file for your shortcode output. This is your shortcode function (e.g., in functions.php): function qt_shortcodez() { return include ‘template/shortcode.php’; } // function qt_shortcodez And that is the very output (i.e., shortcode.php): <?php ob_start(); … Read more
This function returns a string. So you should join the elements of the array to make a string. From the Codex: Function Reference/do shortcode Return Values (string) Content with shortcodes replaced by the output from the shortcode’s handler(s).
Shortcodes are content, equivalent to any other text in the content. There is no way to allow one user to add a shortcode while disallowing another. The only thing that is possible to do is to try to remove any UI the shortcodes have to “hide” it, but in the end the only true solution … Read more
There’s a general convention in WordPress: functions prefixed with the_ will echo a value functions prefixed with get_ or get_the_ will return a value In your case you need to use get_sub_field() instead of the_sub_field() eg: echo do_shortcode( get_sub_field( ‘slideshare’ ) ); The documentation on the ACF site is very comprehensive: http://www.advancedcustomfields.com/resources/functions/get_sub_field/ NOTE: In your … Read more