On: 2008/12/12 Viewed: 22918 times
Shorter URL for this page: http://ozh.in/ku

For plugin developers worrying about compatibility through WordPress versions, it is sometimes important to know when a particular function was implemented (or dropped, even). Sometimes, the WordPress source is commented enough so that information is available. Sometimes, it's not and there is no easy way to obtain this information. I mean, till now of course :)

The WordPress Functions Implementation History

In a trendy axajified manner, the WordPress Functions Implementation History Tool will let you search across nearly 3900 functions through 56 WordPress releases, from 0.71 to 3.0.1

Neat ajax interface to search through all functions in WordPress

Static document

For the curious and those who would like a static list for their documenting needs, I'm also releasing a map of WordPress functions through all these WP versions. It comes in either a compact list (3 columns: function name, introduced in, dropped in), or the complete map (beware, 3900 lines x 56 columns = more than 17 MB table, your browser wont like it)

Light version (680 KB) :
Light version

Mad version (17 MB) :
Full map

More or less noteworthy notes :

  • The regexp pattern used was the following, matching functions declared "standalone" or within classes:
    1. grep -r -e '^\s*function ' * > functions.list
  • Functions from wp-content/ were excluded (i.e. the bundled themes and plugins)
  • Javascript functions were excluded, some of them manually. There might be some survivors though :)

Shorter URL

Want to share or tweet this page? Please use this short URL: http://ozh.in/ku

Metastuff

This page "WordPress Functions Implementation History Tool" was posted on 12/12/2008 at 10:48 pm
Watch this discussion : Comments RSS 2.0.

16 Blablas

  1. 1
    WordPress Functions Implementation Histo... United States »
    pingback on 12/Dec/08 at 10:53 pm # :

    […] Moved here: WordPress Functions Implementation History Tool […]

  2. 2
    When Was This Function Added Or Removed ... United States »
    pingback on 12/Dec/08 at 11:14 pm # :

    […] Getting to know if a function is deprecated, when it was introduced or when it was dropped is important for coders who want to maintain plugins and theme through several WordPress versions. For them, I've updated my WordPress Functions Implementation History Tool […]

  3. 3
    ChaosKaizer Malaysia »
    thought, on 13/Dec/08 at 3:05 am # :

    Thanks this are much needed, can you make WP CONSTANT ref too

  4. 4
    Ozh France »
    thought, on 13/Dec/08 at 12:13 pm # :

    ChaosKaizer » what you want is PHPXREF.

  5. 5
    Joseph Scott United States »
    commented, on 13/Dec/08 at 7:37 pm # :

    Nicely done. I like the auto-suggest feature on the forum.

    A few additional links would be handy was well, like a link to the file that the function was defined in and a Codex link if there is one.

  6. 6
    WordPress News: WordPress 2.7 Awesome, W... United States »
    pingback on 19/Dec/08 at 10:40 pm # :

    […] Functions Implementation History: Along with other looks back at history, Ozh offers the WordPress Functions Implementation History Tool for a look at the changes and options for WordPress functions for coders. It’s important to know […]

  7. 7
    Buscador de funciones de wordpress Spain »
    pingback on 02/Jan/09 at 1:25 am # :

    […] en Planetaozh | […]

  8. 8
    caesarsgrunt Spain »
    replied, on 07/Jan/09 at 7:45 pm # :

    Nice tool, but is there a downloadable version? I'm don't usually have internet access whilst developing plugins and themes…

  9. 9
    Ozh France »
    replied, on 07/Jan/09 at 9:13 pm # :

    caesarsgrunt » The spreadsheets here.

  10. 10
    Benjamin Flesch Germany »
    said, on 22/Jan/09 at 1:19 am # :

    Hello ozh!

    This is a very handy tool – I'll need it when I reach WP plugin development the next time ;-)

    By the way, your translation was very helpful and I've just noticed once more that French is such a beautiful language. It's a shame I cannot speak it really freely.

    Another by the way, this comment has been created with the new easyComment version! :-)

    Best Regards and keep doing these fine things,

    Benjamin

  11. 11
    WordPress Plugins News: Coffee2Code Plug... United States »
    pingback on 05/Apr/09 at 7:16 pm # :

    […] WordPress Functions Implementation History Tool […]

  12. 12
    WordPress Plugins News: Coffee2Code Plug... United States »
    pingback on 12/Apr/09 at 9:21 pm # :

    […] techniques for Plugin and Theme developers, as well as PHP, MySQL, JavaScript, AJAX, and jQuery. WordPress Functions Implementation History Tool ThemeLab – WordPress Template Tag Lookup Tool Validimir Prelovac – WordPress Fundamentals for […]

  13. 13
    Taylor Singapore »
    commented, on 07/May/09 at 5:00 pm # :

    Thanks for sharing, it is useful and informative

  14. 14
    Wizard India »
    wrote, on 19/May/09 at 3:21 pm # :

    Thanks for the article. i would like to know how can i enable my phpbb users to login each time to wordpress using their phpbb login details? That is because i have a lot of users on the forum and i want them to be authors on the blog also. Help appreciated.

  15. 15
    Oliver Germany »
    said, on 07/Jun/09 at 1:09 am # :

    Hey,

    are you planning on updating this for WP 2.8, as it's going to be released in a few days (as they say)? :)

    Thanks for making this, it's saved me a lot of times coding WP plugins.

  16. 16
    R'phael Spindel United States »
    replied, on 29/May/10 at 9:26 pm # :

    2.9.2 to 3.0b2 update please?

Leave a Reply

Comment Guidelines or Die

  • HTML: You can use these tags: <a href=""> <em> <i> <b> <strong> <blockquote>
  • Posting code: Post raw code (no <> &lt; etc) within appropriate tags : [php][/php], [css][/css], [html][/html], [js][/js], [sql][/sql], [xml][/xml], or generic [code][code]
  • Gravatars: Curious about the little images next to each commenter's name ? Go to Gravatar.
  • Spam: Various spam plugins on patrol. I'll put pins in a Voodoo doll if you spam me.
  • I will mark as Spam test comments, all comments with SEO names (ie "My Cool Online Shop" instead of "Joe") or containing forum-like signatures.