Comments on: 4 Checkpoints to Make Sure Plugin Update Notices in WordPress Will Work http://planetozh.com/blog/2008/04/4-checkpoints-to-make-sure-plugin-update-notices-in-wordpress-will-work/?source=rss A bit of my personal life, mainly focused on my kids. A bit of code, mainly focused on Wordpress and PHP. Overall, bits of nothing in particular. Mon, 15 Mar 2010 07:11:52 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: 2008 Plugin Competition Review, Part 2 of 2 « planetOzh http://planetozh.com/blog/2008/04/4-checkpoints-to-make-sure-plugin-update-notices-in-wordpress-will-work/comment-page-1/#comment-65774 2008 Plugin Competition Review, Part 2 of 2 « planetOzh Fri, 08 Aug 2008 15:14:53 +0000 http://planetozh.com/blog/?p=785#comment-65774 [...] way to ensure that WP will always detect when a new version is available (at least according to my empiric observations) On the plus side, I’ll mention that all options are stored within, everybody says it loud [...] [...] way to ensure that WP will always detect when a new version is available (at least according to my empiric observations) On the plus side, I’ll mention that all options are stored within, everybody says it loud [...]

]]> By: Frank http://planetozh.com/blog/2008/04/4-checkpoints-to-make-sure-plugin-update-notices-in-wordpress-will-work/comment-page-1/#comment-50490 Frank Mon, 14 Apr 2008 19:48:47 +0000 http://planetozh.com/blog/?p=785#comment-50490 thx - very nice post and "validator". Best regards Frank thx – very nice post and “validator”.
Best regards
Frank

]]> By: Aaron http://planetozh.com/blog/2008/04/4-checkpoints-to-make-sure-plugin-update-notices-in-wordpress-will-work/comment-page-1/#comment-50246 Aaron Fri, 11 Apr 2008 22:31:29 +0000 http://planetozh.com/blog/?p=785#comment-50246 Like I said on the list, I think there are too many variables to get it to pass. If they want to make everything "perfect" then they need to allow people to assign a random "key" that they can check the database against, but basically killing upgrades through relatively arbitrary inequalities seems a bit much. The plugin folder name should be editable as many users do it anyway. At the very least, there should be an easy way to define what the svn folder name is. Like I said on the list, I think there are too many variables to get it to pass.

If they want to make everything “perfect” then they need to allow people to assign a random “key” that they can check the database against, but basically killing upgrades through relatively arbitrary inequalities seems a bit much.

The plugin folder name should be editable as many users do it anyway. At the very least, there should be an easy way to define what the svn folder name is.

]]>