wp_get_current_user will get you the WP_User object for the currently logged-in user: add_action( ‘wp_ajax_create_team’, ‘create_team’ ); function create_team() { $current_user = wp_get_current_user(); echo $current_user->ID; die; }
Saving data Based on Heartbeat API, you can add custom data to the sent heartbeat on heartbeat-send event in js. This would be used instead of the ajax function you have in your code example. jQuery( document ).on( ‘heartbeat-send’, function ( event, data ) { // Grab the required form data data.location = jQuery(‘input[name=”location”]:checked’).val(); data.userid … Read more
don’t include WP like that. use $_GET instead: … $(“#tags”).autocomplete(“<?php echo add_query_arg(‘get_my’, ‘terms’, home_url()); ?>”, … theme’s functions.php: add_action(‘template_redirect’, ‘terms_for_autocomplete’); function terms_for_autocomplete(){ if(isset($_GET[‘get_my’]) && $_GET[‘get_my’] == ‘terms’): $terms = &get_terms(get_taxonomies()); foreach ($terms as $term) echo “{$term->name}|{$term->name} ({$term->count} results)\n”; die(); endif; }
Nonce You are going to want to set a nonce hidden field or to the element so that you can verify the request. Take a look at the codex for examples. Setting the POST ID and Nonce You will need to add the id of the specific post to the delete button or to a … Read more
Is it the only way to ajaxify your whole site or if there is any better way? No, it’s not the only way. As you already know, you can indeed use .load(). As to what’s better? That’s wide open to debate and depends on personal preference, requirements, circumstances etc. Cannot we use .load() method with … Read more
$.ajax is very simple and you can append more parameters easily in the data: {action:’my_test_ajax’} line, try this: var target=”http://” + window.location.hostname + ‘/wp-admin/admin-ajax.php’; $.ajax({ url: ajax, data: {action:’my_test_ajax’}, type: ‘post’, success: function(data){ console.log(data, data.title, data.content) } }); Make sure the target points exactly to admin-ajax.php or set a global variable (or using localize script) … Read more
I think the solution is amazingly simple here: You’re just missing a single line of code in your ajax callback, namely: global $post; where I assume you’re using: $post = get_post( $post_id ); The reason is that there’s a global post check in the WP_Embed::shortcode() method. More details in my answer here.
probably it’s a bit too late, but it might either help you or others: I just had a similar problem and while looking for the solution I found your question. By now I found a solution for me and it might help you as well. Similar setup to yours, acf_form was loaded, but the location … Read more
There are filters for allowed_http_origins and add_allowed_origins. You can use them to set the proper Access-Control-Allow-Origin header in the response to your AJAX call. Add this to your theme’s functions.php file: add_filter(‘allowed_http_origins’, ‘add_allowed_origins’); function add_allowed_origins($origins) { $origins[] = ‘https://www.yourdomain.com’; return $origins; }
The simple answer: Don’t bother with the Admin AJAX API, use the REST API! Tell WordPress about your endpoint: add_action( ‘rest_api_init’, function () { // register dongsan/v1/whatever register_rest_route( ‘dongsan/v1’, ‘/whatever/’, array( ‘methods’ => ‘POST’, // use POST to call it ‘callback’ => ‘dongsan_whatever’ // call this function ) ); } ); Now we have an … Read more