[wp-hackers] on the role of guid

Dave Ross dave at davidmichaelross.com
Fri Jun 7 01:11:17 UTC 2013

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.
> http://codex.wordpress.org/**Changing_The_Site_URL#**Important_GUID_Note<http://codex.wordpress.org/Changing_The_Site_URL#Important_GUID_Note>
> 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
> hash?
> Doing that will avoid any wrong use of the guid field by less informed
> plugin developers.
> What do you think?
> -f
> ______________________________**_________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
> http://lists.automattic.com/**mailman/listinfo/wp-hackers<http://lists.automattic.com/mailman/listinfo/wp-hackers>

More information about the wp-hackers mailing list