WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#10857 closed defect (bug) (invalid)

Invalid GUID

Reported by: ss44 Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.8.4
Component: General Keywords:
Focuses: Cc:

Description

When importing pages from site A.com into site B.com using wordress's import / export, guids for pages remain those of site A.com rather then changing to be reflective of site B.com

Change History (5)

comment:1 follow-ups: @dd326 years ago

The fact that the GUID's are URL's does not mean that the GUID should be used as a URL.

A Guid is a "Globally Unique ID", Which shouldn't change when the location of the content has changed. As such, Moving between servers shouldnt change the GUID.

comment:2 @hakre6 years ago

  • Keywords reporter-feedback added; guid import removed

dd32 is right, this is not a bug per definition. but keep in mind that the GUID in wordpress is pretty week (do not rely too much on it) because it has never been defined nor documented. It's only describben by the code that implements it.

Please close as invalid.

Maybe the reporter (ss44) can clearify why such a GUID is wrong from her/his point of view? Did this run into any errors?

comment:3 in reply to: ↑ 1 @ss445 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Replying to dd32:

The fact that the GUID's are URL's does not mean that the GUID should be used as a URL.

A Guid is a "Globally Unique ID", Which shouldn't change when the location of the content has changed. As such, Moving between servers shouldnt change the GUID.

The problem I was having was in light of using guid as url rather then using the get_permalink function. Thanks for clearing this up.

comment:4 in reply to: ↑ 1 @johnbillion5 years ago

Replying to dd32:

A Guid is a "Globally Unique ID", Which shouldn't change when the location of the content has changed. As such, Moving between servers shouldnt change the GUID.

This is an interesting issue. If content is exported from A.com and imported into B.com and the GUIDs are unaltered, then the GUID for a particular post/object is no longer a globally unique as it remains present on the original site A.com (assuming the post/object isn't deleted).

If each GUID was changed to reflect the fact the content was now on B.com (as this ticket originally suggested) then the GUIDs would remain globally unique.

I think the OP might have a point.

comment:5 @dd325 years ago

  • Keywords reporter-feedback removed
  • Milestone 2.8.5 deleted

then the GUID for a particular post/object is no longer a globally unique as it remains present on the original site A.com (assuming the post/object isn't deleted).

You're thinking in terms of URL's.

The URL is not unique, But the content contained within IS unique, a post on Possums is a post on possums no matter if its on Site A or site B, as long as the content remains constant. Editing the content should be regarded the same, Its not a new document, Its the same document, however, edited.

Exporting from SiteA to SiteB and retaining SiteA would not really be a valid use-case in my opinion for pro-guid change, as the content should not exist in multipl locations.. one should redirect to the other.

the only real time i can think of that changing the guid should be acceptable, would be moving from private-access site to a public-access site (ie. localhost or dev.site to site.com), That can be done by manually modifying the export however if its wanted.. (find/replace in your favourite file editor)

Note: See TracTickets for help on using tickets.