The main problem are the missing scripts. The scripts enqueued in _WP_Editors::enqueue_scripts() are never printed. The same is true for _WP_Editors::editor_js(). So you have to do that in your AJAX callback handler. I have written a demo plugin and put it on GitHub: T5 AJAX Editor. There is one class named Ajax_Editor. Its method render() … Read more
admin-ajax.php is part of the WordPress AJAX API, and yes, it does handle requests from both backend and front. Try not to worry about the fact that it is in wp-admin. I think that is a strange place for it too, but it is not a security problem in itself. How this relates to “enumerate … Read more
You could just use a RewriteRule to your .htaccess above the regular permalink rewrite rules: RewriteRule ^ajax$ /wp-admin/admin-ajax.php [L] Now send your AJAX requests to example.com/ajax, and never miss core changes to that file after upgrades.
The default response from admin-ajax.php is, die( ‘0’ ); …by adding your own wp_die() or exit() or die() after returning your desired content prevents the default response from admin-ajax.php being returned as well. It also generally means that your ajax call has succeeded. Ultimately, to answer your question, it’s meant to work this way. What … Read more
To get the quicktags to show up, you need to re instantiate them within your ajax oncomplete handler. quicktags({id : ‘editorcontentid’}); My ajax success handler looks like this; success: function(data, textStatus, XMLHttpRequest){ //append editor to dom $(‘#container’).append($(data).html()); //init quicktags quicktags({id : ‘editorcontentid’}); //init tinymce tinymce.init(tinyMCEPreInit.mceInit[‘editorcontentid’]); } I’ve managed to get the editor to load by … Read more
Using wp_die() is the best of those options. As others have noted, there are many reasons to prefer a WordPress-specific function over the plain die or exit: It allows other plugins to hook into the actions called by wp_die(). It allows a special handler for exiting to be used based on context (the behavior of … Read more
I think the only thing missing here is that you need to move add_action(‘wp_ajax_nopriv_ajaxlogin’,’ajax_login’); outside ajax_login_init. That code registers your Ajax handler, but when you only run it on wp_enqueue_scripts, it’s already too late and wp_ajax_nopriv_ hooks are already run. So, have you tried something like this: function ajax_login_init(){ if ( ! is_user_logged_in() || ! … Read more
admin-ajax.php loads wp-load.php: /** Load WordPress Bootstrap */ require_once( dirname( dirname( __FILE__ ) ) . ‘/wp-load.php’ ); wp-load.php loads wp-config.php, and there wp-settings.php is loaded. And here we find this: // Load the functions for the active theme, for both parent and child theme if applicable. if ( ! defined( ‘WP_INSTALLING’ ) || ‘wp-activate.php’ === … Read more
Could you place the action (ajaxConversion) in your Data and check? jQuery.ajax({ type:”POST”, url: ajaxurl, data: { action: “ajaxConversion”, amount: amountToConvert }, success:function(data){ alert(data); }, error: function(errorThrown){ alert(errorThrown); } });
Check the constant DOING_AJAX. Its definition is the first working code in wp-admin/admin-ajax.php. Some very weird plugins, like Jetpack, are defining that constant in unexpected places, so you might include a check for is_admin() as well. Example: if ( is_admin() && defined( ‘DOING_AJAX’ ) && DOING_AJAX ) { // do something } I have asked … Read more