WordPress.org

Forums

[resolved] api.wordpress.org plugin info no php output anymore? (11 posts)

  1. henningsprang
    Member
    Posted 2 years ago #

    Hi,

    Having the company philosophy to use only software packaged as RPM,
    we did package quite a bunch of WordPress Themes and Plugins.

    As with this architecture, we cannot use the Web Interface for Update notification and installation, I wrote a script to go through our package subversion, check each plugin's version, and compare it with the information given from the wordpress api plugin info.

    You could simply call, for example
    http://api.wordpress.org/plugins/info/1.0/authenticator.php
    and get the data nicely in a php serialized way.

    Today I'm trying to run this, but I only get "No input file specified."

    The Json output seems still to work(.json instead of .php) but to use it I had to rewrite my Scripts.

    Before doing so, I'd like to know, is this behaviour a temporary bug that might get fixed some time, or will the Plugin Info not be available anymore in PHP Serialized format?

    Thanks,
    Henning

    [ Please don't bump, that's not permitted here. ]

  2. henningsprang
    Member
    Posted 2 years ago #

    I don't know if that's also considered a bump, but I'm trying to clarify/change the question, as there has been no answer as to of yet:

    Who is actually running the system api.wordpress.org, and how can I contact this person/group?

    I guess they know the answer I'm looking for better than a user/developer forum. Just I see no way how to contact them.

  3. esmi
    Forum Moderator
    Posted 2 years ago #

    Who is actually running the system api.wordpress.org

    It has/is being developed by the wordpress.org core developers. Why API are you referring to? There are quite a few.

    how can I contact this person/group?

    These are the only forums available. And yes, core developers do frequent these forums.

  4. This likely broke when we switched to nginx. Looking into it.

  5. henningsprang
    Member
    Posted 2 years ago #

    O.K.

    So I'm assuming this functionality will keep being there and isn't deprecated - and I'm not going to have to rewrite my packaging scripts, great :)

    If there's anything I can do to help, don't hesitate to let my know!

  6. Andrew Nacin
    Lead Developer
    Posted 2 years ago #

    I wasn't actually aware that plugins/info was configured to work with ".php". Definitely broken at the nginx level. Looking into it.

    That's not to say that you can't still retrieve serialized PHP. I didn't know about .php because this works fine:

    http://api.wordpress.org/plugins/info/1.0/authenticator/

    Much easier. :-)

  7. henningsprang
    Member
    Posted 2 years ago #

    yes, even better.

    I got the info about the api from there, and found not many other docs about it(otherwise it couldn't be called undocumented ;) ) :

    http://ckon.wordpress.com/2010/07/20/undocumented-wordpress-org-plugin-api/

  8. henningsprang
    Member
    Posted 2 years ago #

    And by the way, thanks guys - once i got the right question it didn't take long to get the answer. This api stuff is really cool to write custom packaging and update code :)

  9. salubrio
    Member
    Posted 2 years ago #

    Would this explain why, when searching for plugins within a standalone WordPress installation, no results are returned?

  10. henningsprang
    Member
    Posted 2 years ago #

    Hi salubrio,

    No this API functionality is not used by wordpress itself when looking for updates.
    I only use it in scripts that I've written to check for updates of plugins that I have packaged as RPM for a customer who prefers to deploy them in a native Linux package format and not to depend on checking the web GUI of each installation manually for updates.

    The Blogs that I run with updates over the Web GUI show Updates as usual - I guess as much more people use this, this would have made much bigger waves than this thing here ;)

  11. hectavex
    Member
    Posted 2 years ago #

Topic Closed

This topic has been closed to new replies.

About this Topic