Also it looks really neat on the back end!]]>
On stand-alone sites, any activated plugin can hook WP to run its own update checks. The key word here is “activated”.
On multisite, only plugins activated on the primary site are able to hook the update check process to normally flag its updates. Anything activated only on non primary sites (blog ID > 1) will not be checked. Plugins that host outside w.org need to recognise that and handle it themselves somehow.
EDD’s Software Licensing does a reasonable job of this, but still isn’t perfect. It can’t be, because WordPress multisite isn’t built that way. On multisite, you must be running in the context of the site where the plugin is activated for your plugin’s code to be executed. That includes any update hooks you set.
As Bob says above, Gravity Forms has done a pretty good job here (better, I believe); must look more closely at how exactly…]]>
A sunk cost means something you’ve already paid for and cannot be recovered. So your argument sounds like you’re saying that if you spend $200 or 200 hours on developing your own software, the money or time is gone and can’t be recovered.
That doesn’t mean it’s not worth doing. Which is why I call bullshit. It’s not a sunk cost any more or less than any development is a sunk cost. All work costs something. That’s just the nature of work.
The question is not “Will this cost me time/money?” but “Will this be time/money well spent?” and also “Will this time/money expenditure net me a profit?”
Is spending 200 man hours today in order to save you 12 hours of support tickets in a month when you release an update? Is it worth not being on the front page of Sucuri when your plugin is the latest target of a 0-day exploit? Is it worth the inevitable loss when your userbase loses trust?
Yes. Yes it is.
And if you wanted to save the 200 man hours and spend $200 instead to buy software to do it for you ($239 for Pippin’s EDD software licensing for unlimited sites, $82 for one site), then that’s cheaper (assuming you charge at least $20/hour) but again, comes at a different cost.
But now we’re into understanding the risk and reward of software development, which is a whole different topic.
My point is this.
It’s not a sunk cost. It’s the cost of doing business.]]>
So I’m not saying that it’s not worth it. What I’m saying is that with thousands upon thousand of folks writing and sell plugins it is a sunk cost for any single dev to write this stuff.
So either just use email which is fine for a lot of free low cost usage plugins who don’t use the wordpress repo, use EDD which probably works out to $100 a site by the time you get a payment extension and license keys and another extension or two or write your own.
When you write your own it’s a lot of work that is not trivial. Which in my point.]]>
Really nice work on EDD, Pippin. Impressive job.]]>
Thank you George.
Mika, my deepest apologies.]]>
Everyone keeps telling me I’m insane and maybe we’ll test out yearly licenses again in the future but lifetime free updates solves so many problems, users love it, and I really don’t think we make less money because of it.]]>
Also worth noting… for those that use EDD Software Licensing check out Downloads > Licenses > Expired > Bulk Actions > Send Renewal Notice
^^ Isn’t hard to get a list of past customers that need to be notified about an urgent upgrade.
The difference it makes is phenomenal, not only are significantly more customers running up to date plugin versions, renewal rates associated with those license keys also goes up dramatically, simply by the customer being aware that an update is available.]]>