[wp-trac] [WordPress Trac] #28105: Feature (with patch): allow system-wide inclusion of code
WordPress Trac
noreply at wordpress.org
Fri May 16 14:42:12 UTC 2014
#28105: Feature (with patch): allow system-wide inclusion of code
---------------------------+------------------------------
Reporter: DavidAnderson | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Plugins | Version: trunk
Severity: normal | Resolution:
Keywords: close | Focuses:
---------------------------+------------------------------
Comment (by DavidAnderson):
Hi Denis,
That method with $wp_filter seems to give me what I'm looking for - thank
you.
I can't speak for others, but for myself, being able to register
specifically WP actions and filters is interesting because WordPress is
covering the majority of sites that people want to put onto shared hosting
currently. It's WordPress that the bad guys are hammering with their brute
force attacks, etc. And, of course, code that hooks into WP's filters for
failed logins, or robots.txt, etc., isn't going to run in another CMS, as
far as I can see - i.e. PHP that deals with an IP address of a failed
login (or 100 failed logins, etc.) isn't going to be portable across
different PHP applications without modification for each application.
(Obviously it's portable once you've got the data that "this is a failed
login", but that's the interesting bit - and as I say, it's WP that the
automated attacks are against these days, because of market share.
Targetting even number 2 (is that Joomla?) isn't anything like as economic
for them).
Anyway - so, that unofficial method works. That's good enough for me to
use. I'd still be in favour of an official method, but I'm happy to stop
advocating for it now and to leave it to others, as I've given my view.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28105#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list