[wp-trac] [WordPress Trac] #57107: No-op `MagpieRSS`

[WordPress Trac]

#57107: No-op `MagpieRSS`
-------------------------+------------------------------
 Reporter:  desrosj      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Feeds        |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  2nd-opinion  |     Focuses:
-------------------------+------------------------------

Comment (by Clorith):

 I've done some filtering to remove the false positives from the original
 WPDir search, and add more missed entries I guess... seems to have done a
 good job of it, and gives a much clearer picture of actual usage:
 https://wpdirectory.net/search/01J3JJWDQK27PKB3E0ZPPY1Q93

 The biggest concern I have is that Wordfence appears to use this file as
 the default when checking for path disclosures(?), other than that there
 are some plugins that have been closed (either by the authors them selves,
 or for other reasons, most notably security reasons it seems).

 My main concern is that roughly 50% of them are using `require` statements
 (I've not looked at how many are closed when taking this number), so it
 would potentially cause fatal errors to anyone in those scenarios, unless
 we plan on retaining the file, and noop all the functions within it? Doing
 so would still keep a "dummy" file in the codebase though, which I feel
 we'd want to be able to clean up if we are to remove something that's been
 deprecated this long... (I also just opened #61743 as I think this is a
 place where we can be proactive in the future, perhaps giving that
 priority, and allowing one or two releases of it surfacing such
 deprecations, and then being able to remove these two files is an idea?!)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57107#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform