[wp-hackers] Plugin update checks... SVN path ???
admin at anthologyoi.com
Wed Apr 9 21:07:34 GMT 2008
That's why my plugin isn't showing that it has been updated. I was
wondering why nobody upgraded with the latest release.
test_update_plugin('ajaxd-wordpress'); // works
test_update_plugin('Ajaxd Wordpress'); // works
test_update_plugin("Ajax'd Wordpress"); // works
test_update_plugin('AJAXed WordPress'); // fails
Although, it had worked in the past because I was able to make the
last upgrade with it and the plugin was never released through extend
as "AJAX'd WordPress." +1 for this isn't the way it should work.
Thanks for the heads up.
On Wed, Apr 9, 2008 at 4:55 PM, Ozh <ozh at planetozh.com> wrote:
> For the plugin check thingie to work, I thought the deal was: make
> sure that the plugin name in the plugin's header and in its readme.txt
> are the same.
> Am I completely missing something obvious ?
> To test things further, I've set up this piece of quick code that
> pretends to send only one plugin with version 0.1 to the API server,
> and see what it returns:
> Usage is simple: test_update_plugin('Your Plugin Name')
> - my plugin's header is :
> Plugin Name: Admin Drop Down Menu
> - my readme.txt starts with:
> === Admin Drop Down Menu ===
> test_update_plugin('Admin Drop Down Menu'); // returns nothing, the
> API server doesnt notice any update
> But now, if instead of the plugin name, I check with its *SVN path*
> (my plugin is in
> test_update_plugin('ozh-admin-drop-down-menu'); // works
> test_update_plugin('Ozh Admin Drop Down Menu'); // works
> SVN directory name and plugin name should be allowed to be different,
> just as plugin name and the filename itself ('My Super Plugin' vs
> joe_myplugin.php) can be different.
> So, my point is : this is totally *not* how I expected things to work :)
> http://FrenchFragFactory.net ~ Daily Quake News
> http://planetOzh.com ~ Blog and WordPress Stuff
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers