Timeline for Is there a better way of handling AJAX requests in Wordpress?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2016 at 19:15 | comment | added | connorb | I'm think I'm going to rip parts of the REST API to build a basic route callback system which should suffice for what I'm trying to achieve. Thanks for the help. | |
| Aug 20, 2016 at 19:05 | comment | added | Rarst |
I am not sure what heartbeat thing you refer to. Any request to admin-ajax.php performs full core load, I am not aware of that changing and it's unlikely it ever will (with WP's commitment to extreme backwards compatibility).
|
|
| Aug 20, 2016 at 19:03 | history | edited | Rarst | CC BY-SA 3.0 |
edited body
|
| Aug 20, 2016 at 18:44 | comment | added | connorb |
"The main problem with native ajax endpoint is that it had to load whole WordPress core." - Is this still the case (WP 4.6), I assume that is why the 'heartbeat' was necessary to determine when the core had loaded completely or to a sufficient extent that the admin-ajax endpoint could successfully parse requests?
|
|
| Aug 20, 2016 at 17:59 | history | answered | Rarst | CC BY-SA 3.0 |