the_guid(); pulling old wordpress address

  • Resolved futureprogress

    (@futureprogress)


    19 years, 2 months ago

    In my RSS2 feed:
    http://futureprogress.net/feed/

    You will find that my the_guid(); (in wp_rss2.php) outputs both my production wordpress URI and my dev URI:

    Production example:
    <guid isPermaLink="false">http://futureprogress.net/-/2007/03/28/on-hacking/</guid>

    Dev example:
    <guid isPermaLink="false">http://futureprogress.net.s4954.gridserver.com/?p=5</guid>

    It appears that when I posted the older posts under the dev config, that URI was saved and does not update even though I have changed the main URI to prod and hence newer posts contain the prod URI

    Is there a way to force update whatever it is the_guid(); is grabbing?

    Thanks…

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter futureprogress

    (@futureprogress)

    19 years, 2 months ago

    Well I found the guid column in my wp_posts and it appears that I need to edit that.

    However, I am still curious….is this the only way to update the guid field?

    Thanks in advance for any insight…

    Thread Starter futureprogress

    (@futureprogress)

    19 years, 2 months ago

    OK, so while looking at the logistics of modifying my guid field manually to change ’em to my production URI, I am really hoping there is a force update method or something similiar.

    What does one do to update guid URIs when moving a blog?

    Chris_K

    (@handysolo)

    19 years, 2 months ago

    Why would you change ’em? They’re not part of your URL. They’re “just” a guid.

    What am I missing?

    Thread Starter futureprogress

    (@futureprogress)

    19 years, 2 months ago

    Well technically….since its a GUID and isPermaLink="false" it matters little…I just feel its sloppy….regardless of their utility, WP uses URIs as GUIDs which at this point are dead or invalid…

    After reviewing some of the old posts, I take it your stance is that it doesn’t matter….but as I said…it is sloppy….but not worth the work to update at this point.

    Anyway, I will set this as resolved.

    Thanks again Handy 🙂

    Chris_K

    (@handysolo)

    19 years, 2 months ago

    I seem to recall some discussion of it on the Hackers List not too long ago. SOO much fun to search those (ok, not!).

    Perhaps start here for some light reading: http://comox.textdrive.com/pipermail/wp-hackers/2006-October/008952.html (then view by thread to see responses)

    Moderator Samuel Wood (Otto)

    (@otto42)

    ww.wp.xz.cn Admin

    19 years, 2 months ago

    The short of it is that the GUID is just a string. WordPress uses a permalink there at the time the post is made, but honestly, it doesn’t make any difference what the GUID is, as long as it’s unique. And, in theory, it is never supposed to change. That’s sort of the whole point of a GUID. Readers can use it to determine if an item is new or not by remembering the GUID’s they already knew about.

    Thread Starter futureprogress

    (@futureprogress)

    19 years, 2 months ago

    Again, technically it does not matter — yet I would agree with this:

    http://diveintomark.org/archives/2004/05/28/howto-atom-id#nohttp

    Moderator Samuel Wood (Otto)

    (@otto42)

    ww.wp.xz.cn Admin

    19 years, 2 months ago

    I wonder, is there any particular reason that sites don’t just generate UUID‘s? I mean, they’re standardized, the odds are way, way long against duplicates, etc…

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘the_guid(); pulling old wordpress address’ is closed to new replies.

Tags