Current, future-proof functions will soon be required of themes sold on ThemeForest

6 Comments

Siddharth, a member of the Envato team, shared on their Notes blog that stricter policies are on the way for authors submitting WordPress themes to their ThemeForest marketplace, specifically regarding deprecated functions.

Deprecated functions, if you’ll allow the quick explanation, are those functions that the WordPress core developers send to the proverbial graveyard with each major release. These functions are no longer recommended, and are usually replaced by something more useful and more future-proof.

Siddharth said that while their policy toward deprecated functions is “a bit lenient at the moment”, this will change. He said that “[they] only dock an author if the tag being used is too old and has a completely better alternative,” but that in the future authors will be required to use only current functions within their submitted themes.

For the developers reading: do you find yourselves using deprecated functions often, or do you police yourselves well? For those out there regularly purchasing themes: how important is the use of current functions to your buying decisions?

6 thoughts on “Current, future-proof functions will soon be required of themes sold on ThemeForest

  1. I imagine that the only people who use deprecated functions are the same ones who don’t know they exist. And for those who do, there’s a handy developer’s plugin called Log Deprecated Notices.

    Simply turning on WP_DEBUG goes such a long way to identifying areas for improvement in code, ranging from deprecated functions to streams of PHP notices.

    If I were running a premium theme marketplace, I’d use the same basic standards as the WordPress Themes Directory — force the theme to pass the Theme Check plugin and be entirely be free of notices, not just ones marking deprecated functions.

    • Actually ThemeForest has already been doing this for sometime. I think now it will just be official.

      • Sure, I believe that they have recognized what the best practice is. It’s still encouraging that before long they may start turning away themes that don’t follow best practices.

  2. I always develop with WP_DEBUG on. I don’t know why anyone wouldn’t!

    It makes debugging errors so much easier, and because of the way WordPress is set up, it tells you the deprecated commands, and what to replace the commands with.

  3. Y’all beat me to the punch. I’d love to see all theme shops (myself included) make the pledge to run their demo sites with WP_DEBUG(‘true’); for a day. It’d be the closest thing to x-ray vision.

Comments are closed.