[wp-hackers] wp-admin folder and admin-ajax.php

Gavin Pearce Gavin.Pearce at 3seven9.com
Tue Aug 10 08:31:55 UTC 2010

Hi Andrew,

As per my email - that doesn't really address the issue, or suggest why
the ticket was closed. The resolution in the ticket states:

"admin-ajax.php can be used (and is better for) for front-end/nopriv
AJAX requests".

I understand it "can" be used - but in what way is it "better"?

Being the only file within wp-admin that is required sometimes by the
front-end, just because "it works", doesn't seem a valid reason?

In the ticket, just before removing the file, TobaisBG raises some good
points that seem to have been missed. If a site has htaccess restriction
on the wp-admin area, as suggested in various places in the CODEX (and
not altogether a bad idea), this will break any plugins that rely on
AJAX. You can't expect plugin developers to ask people to modify their
htaccess files to get their plugin to work... Let's not even begin on
SSL ...


-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Andrew
Sent: 10 August 2010 05:11
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] wp-admin folder and admin-ajax.php

On Mon, Aug 9, 2010 at 5:27 PM, Lox <lox.dev at knc.nc> wrote:

> 2010/8/10 Andrew Nacin <wp at andrewnacin.com>:
> > Aside from the reasons highlighted in the post, I've additionally
> > cross-referenced the dev chat from March 25
> > http://core.trac.wordpress.org/ticket/12400#comment:29
> I wonder why the front-end ajax was added and then removed:
> nacin - 5 months ago
>    * status changed from reopened to closed
>    * resolution set to fixed
> (In [13828]) Remove wp-ajax.php. admin-ajax.php can be used (and is
> better for) for front-end/nopriv AJAX requests. fixes #12400

Your answer can be found in the ticket and dev chat that's already been
linked to.
wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list