Title: cbanack's Replies | WordPress.org --- # cbanack [ ](https://wordpress.org/support/users/cbanack/) * [Profile](https://wordpress.org/support/users/cbanack/) * [Topics Started](https://wordpress.org/support/users/cbanack/topics/) * [Replies Created](https://wordpress.org/support/users/cbanack/replies/) * [Reviews Written](https://wordpress.org/support/users/cbanack/reviews/) * [Topics Replied To](https://wordpress.org/support/users/cbanack/replied-to/) * [Engagements](https://wordpress.org/support/users/cbanack/engagements/) * [Favorites](https://wordpress.org/support/users/cbanack/favorites/) Search replies: ## Forum Replies Created Viewing 4 replies - 1 through 4 (of 4 total) * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [Easy fix for Common RSS/Atom feed Bug](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/) * Thread Starter [cbanack](https://wordpress.org/support/users/cbanack/) * (@cbanack) * [17 years, 2 months ago](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/#post-980230) * > Working around bugs in plugins is not something that should be in the core. > There’s no “patch” in WordPress that can fix code in somebody else’s unrelated > code. It’s a losing battle. * Well, obviously we disagree on this point–although to be fair, I’m not really recommending that you write a “work around” for someone else’s bug so much as I am recommending that you find a way to bullet-proof your code so that it’s not so easy for plugin developers to accidentally break feeds. * If what you say is true and the main cause of this problem is not plugin developers, but badly edited wp-config.php files, then it sounds like you’ve already done something to make things more bulletproof. Hopefully that means that this issue won’t be so common in the future. * As for me, I’m still gonna have to go digging to figure out which one of my plugins is misbehaving! * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [Easy fix for Common RSS/Atom feed Bug](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/) * Thread Starter [cbanack](https://wordpress.org/support/users/cbanack/) * (@cbanack) * [17 years, 2 months ago](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/#post-980228) * Well, I honestly don’t mean to offend anyone here, but I think that simply saying“ MY codebase works fine, so it’s not MY problem” is a bit stubborn, as well as a bit naive. * I am the team lead for a software application that also uses plugins, and we consider it very important to make our software bullet-proof. One of our main architectural goals is to sandbox everything so that even a maliciously written plugin can’t break our application. This is a lot harder to do with php than it is with Java, but at the very least I would think you’d be interested in making your software as robust as possible. The issue I’ve raised is a common one, and it’s not making the plugin developers look incompetent, it’s making the WP developers look incompetent! And yes, I fully understand that the WP developers didn’t write the bug…but the bug is still there. * If using output buffering is unacceptable, then how about adding a bit of code in the next release that checks the rss/atom feeds each time a plugin is activated? It should be easy enough to detect the extra newlines and refuse to activate the plugin (with a helpful error message, so that plugin writers can quickly spot and fix the problem in their own code.) * Again, my intention here is to be helpful, not abrasive. I suppose this could be one of those issues where the WP devs get their back up, and nothing I say( no matter how sensible) will change your minds. If so, you’ll just have to forgive my annoyance; I’m going to be stuck patching WordPress by hand from now on, or at least until I can find an alternative that works with plugins *without* forcing me to fix them first. * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [Easy fix for Common RSS/Atom feed Bug](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/) * Thread Starter [cbanack](https://wordpress.org/support/users/cbanack/) * (@cbanack) * [17 years, 2 months ago](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/#post-980219) * Too bad, because this is such a simple problem to fix. * The issue has been raised in TRAC (you can log in using the same details you use to log into this forum.) * [https://core.trac.wordpress.org/ticket/108](https://core.trac.wordpress.org/ticket/108) * Feel free to jump in there and add your two cents. If the issue gets enough attention, perhaps one of the devs will fix it. * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [Easy fix for Common RSS/Atom feed Bug](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/) * Thread Starter [cbanack](https://wordpress.org/support/users/cbanack/) * (@cbanack) * [17 years, 3 months ago](https://wordpress.org/support/topic/easy-fix-for-common-rssatom-feed-bug/#post-980110) * Yup…that’s exactly what I’m hoping will happen. It’s an awfully easy change, and a big win. Viewing 4 replies - 1 through 4 (of 4 total)