I saw an interesting comment from Andy Skelton over here:

“Hey there! Nice work on this plugin/widget code. However, it won’t work on future versions of WordPress because you’ve queried a table that will no longer be available. Links are tricky business these days… :-)

Interesting. The widget I just wrote also queries the database table directly. The API doesn’t allow for much manipulation of the links, as it has anchor tags hard-coded in (not viable for use in a drop down list).

I’m wondering if there is a reference online for how newer versions will change in regards to this? I’m assuming he’s referring to WP 2.1.

It would also be nice if the API allowed for a way to use the data like I am, without needing to re-implement the functions to format them appropriately. get_archives() was designed intelligently for this type of use. Unfortunately get_links() and list_cats() are not.

Bookmark the permalink.

5 Responses to Hmmm.

  1. adam says:

    yeah, his response was certainly cryptic.
    i guess the thing to do now is submit API bugs for any functions with hard-coded formatting. =/

  2. Pingback: sunburntkamel » Blog Archive » My widget sucks

  3. Andy Skelton says:

    Hey there! 🙂 The thing to do now, actually, is run a test blog using the latest builds (svn or nightlies) and join the wp-hackers and wp-testers mailing lists. There is not any documentation for 2.1 yet, so if you want to future-proof your code you’ll have to keep up with core development.

  4. michael says:

    please e=mail me
    double column issue

  5. cat litter says:

    *taps fingers on desk and wonders why nobody is postin*

    \”Postin\” -Southern Verb, to post. lol