WordPress Ideas » Tag: deprecated code - Recent Posts

Ipstenu (Mika Epstein) on "plugins should be developed with wp_debug set"

Ipstenu (Mika Epstein) — Thu, 24 Jan 2013 01:58:03 +0000

Sorry about the delay on approving posts. I've been extra busy.

Stop posting so often and you'll stop getting caught as spam ;) It's not a complex system, but a lot of 'yeah!" and 'Me too!' posts trip the filter.

Also? Posting plugin ideas here isn't a -core- WordPress idea.

LeyCosmica on "plugins should be developed with wp_debug set"

LeyCosmica — Thu, 03 Jan 2013 11:06:01 +0000

Here I show you my post on chat: http://www.wordpress.org/extend/ideas/topic/put-chat-on-wordpress

Thanks!

prophecy2040 on "plugins should be developed with wp_debug set"

prophecy2040 — Tue, 13 Nov 2012 06:09:13 +0000

Thanks Mika!

Regards,
Don

Ipstenu (Mika Epstein) on "plugins should be developed with wp_debug set"

Ipstenu (Mika Epstein) — Tue, 13 Nov 2012 01:05:10 +0000

We;'re working on that, Don.

prophecy2040 on "plugins should be developed with wp_debug set"

prophecy2040 — Mon, 12 Nov 2012 20:00:46 +0000

I think it would be more beneficial for WordPress to have a method to check the plugin (as a developer) to see if it is using any deprecated calls (like a new Admin Tab in the Repository, "Check My Plugin" or something. If a plugin is found to be using deprecated calls, the developer should be notified as such and given some suggestions on how to fix it.

As a plugin developer, I know that it is sometimes difficult to keep up with WordPress changes - especially when you are offering more than one plugin to the WordPress community.

I agree there should be some check, but I am not sure requiring WP_DEBUG testing is really the answer. It also makes it sound like developers are at fault - but we have no control over what WordPress decides to deprecate or replace, or when they decide to do it. You could have a plugin that is clean and free of deprecated calls, and 3 months later it could have 20 deprecated calls because it uses one recently deprecated function.

I LOVE WordPress, and I like to help out the community, but if it got too difficult to offer my plugins to the world, I would stop supporting or developing them for everyone else, and just do it for myself. It takes a lot of time to keep plugins up to date between WP changes - that's why I think it would be better if they helped us out a bit by notifying us that something might be wrong with our plugin - or it might need to be updated.

Thanks for listening.
Don Fischer

Wikibiz on "plugins should be developed with wp_debug set"

Wikibiz — Mon, 12 Nov 2012 18:36:38 +0000

Agree. The mechanism of adding plugins now is very loose

rencontre cougar on "plugins should be developed with wp_debug set"

rencontre cougar — Mon, 22 Oct 2012 08:37:10 +0000

Clearly that would be a good feature to add, good thinking dude...

fuckofnickname on "plugins should be developed with wp_debug set"

fuckofnickname — Thu, 30 Aug 2012 21:13:11 +0000

cubecolour on "plugins should be developed with wp_debug set"

cubecolour — Sat, 10 Mar 2012 11:02:32 +0000

I think it would be beneficial to have a requirement that plugins hosted on WordPress.org should be tested with WP_DEBUG set to true. Many plugins are using deprecated code or have undefined variables and other warnings.

All this would need is an additional line in the plugin guidelines that states this as a rule of inclusion. Then when plugins are found not to be in compliance, the plugin author can be referred to a page that explains how to deal with the common errors.