Your add_action() calls for the AJAX handlers are too late. Add these hooks earlier, the best action is probably wp_loaded: add_action( ‘wp_loaded’, ‘register_ajax_handlers’ ); function register_ajax_handlers() { add_action( ‘wp_ajax_jp_ajax_request’, ‘jp_ajax_process’); add_action( ‘wp_ajax_nopriv_jp_ajax_request’, ‘jp_ajax_process’); } See also: Debug AJAX. This code should be placed in a plugin or in your theme’s functions.php.
I was able to get multiple wp_ajax_ functions to declare callback functions like this: add_action( ‘init’, ‘my_ajax_init’ ); function my_ajax_init() { add_action(‘wp_ajax_nopriv_wpa56343_search’, ‘first_search’); add_action(‘wp_ajax_wpa56343_search’, ‘first_search’); } add_action( ‘init’, ‘my_ajax_no_geo_init’ ); function my_ajax_no_geo_init() { add_action(‘wp_ajax_nopriv_nogeo_results’, ‘second_search’); add_action(‘wp_ajax_nogeo_results’, ‘second_search’); }
Ok so it actually looks like there is a couple of ways you could do this. The first one is by changing your $list into an array and returning it as JSON. It will be easy to change $list to an array by just adding it like this: $list[] = ‘<option value=”‘.$term->term_id.'”>’.$term->name.'</option>’; Then return it … Read more
In WordPress Ajax works this way: First, you register the ajax action and the function you want to use to serve that action, of course, you have to write that function. All the request go to the same URL wp-admin/admin-ajax.php, what it changes is the action, and depending on the action, a different function is … Read more
Ajax endpoint is known to be relatively slow, but that primarily comes from loading WordPress core. If you are seeing drastic difference between two endpoints (native Ajax vs yours custom) that both perform core load, then something is doing something that degrades Ajax endpoint on top of it. I would profile Ajax endpoint to have … Read more
The problem is that about.php is not a recognized file by WordPress and won’t load any of the actual WordPress functions. <?php wp_header(); ?> in your themes header.php file actually loads most the WordPress functionality that you’re used to using. Since you’re not calling either get_header() OR wp_header() in your about.php file you don’t actually … Read more
When you send an AJAX request, wp-admin/admin-ajax.php is called, not your template file. This separate request has no knowledge of all existing code in all existing templates, because they aren’t even included. What is included: the theme’s functions.php and plugin files. This is why your callback works in a plugin. As a rule of thumb: … Read more
This will not work due to the “same-origin policy” unless that server you are trying to reach specifically allows these type of requests with something like Access-Control-Allow-Origin: *. You can read the documentation on MDN in order to get more information about this topic. From my tests, the server will also need another header configured … Read more
I think your php add_to_cart function not setting cart cookies, you can do this manually by adding this line inside the if condition before //$added line add this line do_action( ‘woocommerce_set_cart_cookies’, TRUE ); this will set cart cookies.
You just have your arguments lined up wrong. Change the line to wp_enqueue_script( ‘ajax-products’, plugins_url( ‘/js/ajax.js’, __FILE__ ), array(‘jquery’), ‘1.2’, false ); You can use plugins_url() with the second parameter of __FILE__ to get the directory of the specific pluign, and in the first argument you pass the relative location of your script. The rest … Read more