Comments on: Enable Automatic Updates for Plugins Hosted by Developers

By: shawn

shawn — Sun, 11 Jul 2010 14:02:43 +0000

Thanks a Mil!!!

Shawn

By: Kaspars

Kaspars — Sun, 11 Jul 2010 12:27:59 +0000

Here is the code for WordPress 3.0.

By: shawn

shawn — Sun, 11 Jul 2010 12:15:59 +0000

Nice work here, any idea when the article this will be published, or is there any way to get the working sample!

Thanks for the time man!

By: kaspars

kaspars — Mon, 10 May 2010 20:06:45 +0000

Jeff, there is a new post coming that will showcase code examples for both plugin and theme automatic updates which work with WordPress 3.0 (that posts is already in Drafts).

By: Jeff Rose

Jeff Rose — Mon, 10 May 2010 15:03:46 +0000

Kaspars, I noticed that you removed the .txt files this post refers to. Any chance you are willing to share this code still?

By: Arno

Arno — Sun, 11 Apr 2010 00:15:04 +0000

that’s great, thank you so much!

By: Kaspars

Kaspars — Sun, 11 Apr 2010 00:05:22 +0000

Good news, Arno -- I got it all working just five minutes ago. I have working examples of both plugin and theme that use custom API. I'll send you the files right now, as it will take a while to write an article that explains it all.

By: Arno

Arno — Sat, 10 Apr 2010 20:48:02 +0000

wow, this is very good news! thank you for your effort.

By: Kaspars

Kaspars — Sat, 10 Apr 2010 20:41:18 +0000

Arno, in several hours (or days) I'll publish a new article that gives examples of automatic updates both for themes and plugins. So stay tuned.

By: Arno

Arno — Fri, 09 Apr 2010 14:13:01 +0000

hey kaspars-

first of all, thanks for this. it already helped me a lot. I had some difficulty getting this to work, though (wordpress 2.9.2)
whenever I enabled the get_transient(‘update_plugins’) line, the plugin refused to work. without it, everything seemed fine. so I did not investigate further. but one thing happened every time I updated my plugin through this mechanism: wordpress did not replace the existing plugin file, but disabled it, created a new folder with .tmp appended and put the new plugin version there, then enabled the new one.
still half of what I wanted, but I guess it’d be great if people didn’t have to delete their old plugin files afterwards.

do you have an idea what this could be related to? my “official” plugins all work fine and updating them does too.
I’d be thrilled if you shared your thoughts on this. I realize this post is already some months old, but I’m hoping you will still get my message.

best regards,
arno