[wp-hackers] WordPress Plugin GUID

Stephen Rider wp-hackers at striderweb.com
Sun Jun 7 00:01:15 GMT 2009

On Jun 6, 2009, at 2:48 AM, Eric Marden wrote:

>> The packager adds the GUID automatically.
>> Of course, we *would* need some sort of "transition" system , since  
>> plugins already installed would not get the GUID until the next  
>> time they're updated.
>> Or is that what you meant? ;-)
> Unless the packager is zipping them on the fly, wouldn't the mere  
> change of the readme.txt in svn be enough to trigger the update  
> (especially if a .1 is added to the version number, if it depends on  
> that too)?

if I already have Plugin X installed on my blog when this system is  
instituted, I would not get the GUID until the next update to that  
plugin.  Thus some sort of transitory system would have to be in place  
so that that first update still happens.  Two possibilities come to  

1) Brute force method: up the version every single plugin in Extend  
with a .1 on the end, adding the GUID.  I do **not** think this one is  
a good idea....

2) The system remembers the extant version for each plugin at the time  
the system is instituted, and basically upgrades a plugin if it's at  
version #x or below, OR it has the GUID.  This way could work. :)

More information about the wp-hackers mailing list