Are there any Console js errors? The admin-ajax.php is WordPress’s built in way of dealing with ajax so you should probably do something like this, assuming .get() would also work: $.post(ajaxurl, data, function(response) { alert(‘Got this from the server: ‘ + response); }); http://codex.wordpress.org/AJAX_in_Plugins
Your McAdmin seems fine – the problem is likely one of two reasons: Another AJAX hook for blubb is terminating the script before McAdmin::get_vehicle You need to add the same hook for wp_ajax_nopriv_blubb – for non-logged in AJAX requests (otherwise it fails silently). If neither is the cause, you need to do a little HTTP … Read more
Filtrify doesn’t actually use AJAX to get a new data set, it simply hides all of the elements which don’t match your current filter. Because you already have a page displaying all books (for example) you are already pretty well set up to use Filtrify. The only extra step that you need to take is … Read more
You are using esc_attr(), which isn’t available if you use define( ‘SHORTINIT’, true ); , see source. So you either have to load the formatting.php manually or have to ditch the define( ‘SHORTINIT’, true ); – actually like the example in the thread you are referring to shows. As said in the comment, I checked … Read more
From quick look at your code you seem to be omitting where you are submitting request to. By default it is just current page, which isn’t typically equipped to receive the request. Since you are using wp_ajax_ hook you need to point request at admin-ajax.php endpoint. On admin side the URL is provided in ajaxurl … Read more
This question is old, but for future reference, check out the answer I gave on the original question here. The gist is: Confirmation Dialog The alert is generated in wp-admin/js/post.js and wp-includes/js/autosave.js. Theoretically, you should be able to use the following line of code in your $.post success function: wp.autosave.initialCompareString = wp.autosave.getCompareString(); But that doesn’t … Read more
I think your paradigm is not optimal. You are starting on premise of “WordPress Ajax endpoint is slow” and your solution is to “build alternate authentication scheme”. This completely spells trouble. Anything security should be reused as much as possible and coded by people specializing in security. Trade-off of reimplementing security for the sake of … Read more
You can use like this for send ajax… function my_action_javascript() { ?> <script type=”text/javascript”> jQuery(document).ready(function ($) { var data = { ‘action’: ‘my_action’, ‘whatever’: ‘1’ }; $.post(ajaxurl, data, function (response) { if ($(‘#menu_order’).val() == ” || $(‘#menu_order’).val() == ‘0’) $(‘#menu_order’).val(response); }); }); </script> <?php } add_action(‘admin_footer’, ‘my_action_javascript’); function my_action_callback() { $whatever = intval($_POST[‘whatever’]); //$whatever += … Read more
The issue is with this line: wp_localize_script( ‘ajaxHandle’, ‘myAjax’, array( ‘ajaxurl’ => admin_url( ‘admin_ajax.php’ ) ) ); It should be admin-ajax.php instead of admin_ajax.php.
There isn’t much point to distinguishing admin-ajax.php since it’s essentially same file with same logic running for many many purposes. You are passing action data and hooking into respective action. So action is your identifier. If you are reusing same action and need to further differentiate — just pass more data with your GET/POST request … Read more