In WordPress 3.4 you have something called Theme Customizer that provide a optionpanel within wp-admin that enables you to see the changes in real-time. Maybe thats an option to go? Look at this video to see how it works: http://www.youtube.com/embed/amUjCfpIsJ4 Then you have themes like Headway that you can change the theme appearance on the … Read more
After some digging, I decided to try a hunch and it ended up working. Whether this is the sanctioned solution or not, but it has worked in my testing. For the AJAX url, add the $_GET variable ?action=[ajax_action] where [ajax_action] is your requested action. (ie. http://www.example.com/wp-admin/admin-ajax.php?action=[ajax_action]) Then make add_action(‘wp_ajax_nopriv_…’) include your action variable, ie. add_action(‘wp_ajax_nopriv_[ajax_action]’, … Read more
You have a typo: wp_ajax_ ajaxfunction. there’s a space after the underscore. also, use wp_localize_script to set your admin-ajax path: wp_enqueue_script( ‘contact’, get_bloginfo(‘template_directory’) . ‘/subscribe.js’, array(‘jquery’), ‘1.0’ ); wp_localize_script( ‘contact’, ‘ContactAjax’, array( ‘ajaxurl’ => admin_url( ‘admin-ajax.php’ ) ) ); then in your javascript, use ContactAjax.ajaxurl
Your stand-alone file doesn’t know the WordPress constants and functions. Use the native WordPress AJAX API instead. See also: What’s the preferred method of writing AJAX-enabled plugins? In short: Put all your custom code into a function or a class and hook from your plugin into … add_action(‘wp_ajax_ACTION_NAME’, ‘your_function’); … and … add_action(‘wp_ajax_nopriv_ACTION_NAME’, ‘your_function’); Replace … Read more
1st) Add another dependency: array( ‘json2’, ‘jquery’ );. 2nd) Dig into wp-localize-script and read about wp-localize-script() in Codex. It allows you to send data from PHP to javascript via an javascript var, set in PHP (as 2nd arg for wp_localize_script()).
Here´s something to get you started. Adapt the code below to your needs Create an init.js file with notepad and paste your code in there Save it in a logical place your theme folder (the JS directory for example) Register and enqueue this file (make sure to load it after jquery) Datepicker set up: /* … Read more
you’re deregistering jquery, then registering it under the handle js-scripts, but then specifying the jquery handle as a dependency for your other scripts. also, use the wp_enqueue_scripts hook for wp_enqueue_scripts function, not wp_head. the appended version doesn’t matter, but you can pass null as version parameter to get rid of it completely if you want.
Sure. Set the fifth parameter of wp_enqueue_script or wp_register_script as true, and that script will be placed in the footer. For example, your line wp_register_script(‘jquery’, (“http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js”), false, ‘1.7.1’); should be wp_register_script(‘jquery’, (“http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js”), false, ‘1.7.1’, true); And if you ever don’t need/want to specify a version number, just set the fourth parameter to false. More info: … Read more
There’s a reason, why one should use the proper hook, which – in this case – is wp_enqueue_scripts. Then always keep in mind, that some plugins might require a dependency/are dependent on another Javascript library like jQuery. Now this example shows you how to enqueue your script With the right path/URI API function With jQuery … Read more
if you want it on all single posts as well as pages & custom post types, use is_singular() instead of is_single() & just in case you’re using it on the template, this code goes in functions.php UPDATE IN RESPONSE TO THE COMMENTS write this code just above your wp_head() function in header.php global $wp_scripts; var_dump($wp_scripts); … Read more