[wp-hackers] on the role of guid
danielx386 at gmail.com
Fri Jun 7 01:20:43 UTC 2013
Someone did put in a GSoC on this and it was rejected. I think there
was other things that needed to be sorted out first.
On Fri, Jun 7, 2013 at 11:11 AM, Dave Ross <dave at davidmichaelross.com> wrote:
> There's been talk of changing the field to a UUID, or at least adding a new
> column for a proper UUID. You're right, plugins shouldn't be using that
> field as a permalink, but they do. And even if they're wrong, they're out
> Someone even submitted a GSoC proposal for setting up a proper UUID. I
> don't think it was accepted, but it would be nice to see someone try
> building an implementation and seeing what issues crop up with different
> plugins & themes.
> On Wed, Jun 5, 2013 at 6:14 AM, Fabrizio Regini <freegenie at gmail.com> wrote:
>> Hi everybody,
>> I was looking for info about the guid field in wp_posts and I stumbled on
>> this page, which states that you should never-ever change the guid field
>> even if you change your site's domain.
>> I've recently started to hack around some wordpress plugins, and I noted
>> that at least one of those I encountered rely on the guid field as a source
>> of redirect.
>> As I understand this is clearly in contrast with guidelines as described
>> in the above page. If the guid field is to be used as a globally unique
>> identifier for the post, wouldn't it be better to rely on a kind of SHA
>> Doing that will avoid any wrong use of the guid field by less informed
>> plugin developers.
>> What do you think?
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers