GUID & WPE Legacy Network

  • WP Engine’s legacy network is being phased out. It is my understanding that domains containing wpengine.com will no longer function after the phase out.

    Many of my sites have GUIDs like https://clientname.wpengine.com/?p=1.

    https://bettersearchreplace.com/doc/running-a-search-replace/ suggests that GUIDs should only be changed before a site goes live. However, given the situation, it seems best to replace https://clientname.wpengine.com/ with https://www.clientname.com/. Does that seem sensible to others?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)

  • Hi there,

    Better Search Replace Team here. Thanks for reaching out with your query we would be happy to assist.

    It is not recommended to change the GUID, especially for live sites because it serves as a unique identifier. Changing it may cause some issues, for example, if you have a GUID with different domains like domain1.com/?p=1 and domain2.com/?p=1, once you replace domain1.com with domain2.com, you’ll have two posts with the same GUID (domain2.com/?p=1) and that might error out. However, if you are 100% sure that your GUIDs are consistent (using domain1.com for all), then you can probably replace the GUIDs but it’s really not necessary because it’s just internal, so it’s best to have it preserved. I found this article online that explains this a bit further: https://zeropointdevelopment.com/why-you-should-never-change-the-guid-but-maybe-sometimes/

    I hope that helps!

Viewing 1 replies (of 1 total)
  • The topic ‘GUID & WPE Legacy Network’ is closed to new replies.

Tags