WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #18769


Ignore:
Timestamp:
09/24/2011 11:11:14 PM (9 years ago)
Author:
nacin
Comment:

There is a RELOCATE constant that can be set, which will allow wp-login.php to work, and upon login the siteurl setting will be updated.

We can potentially handle this more gracefully, by not requiring the constant and having some sort of migration step/warning. But do we want that? Seems pretty rare/edge to be honest (possibly the first bug report I've seen on this specifically). And then there's the issue with old URLs breaking, so it's not like we'd want to encourage migrations as we won't be able to handle the old URLs.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18769 – Description

    initial v1  
    1 We manage a lot of users who have Wordpress blogs, and probably the number one user support request we have to field comes out of this situation:
     1We manage a lot of users who have WordPress blogs, and probably the number one user support request we have to field comes out of this situation:
    22
    3 1. User decides they want to move their Wordpress,
     31. User decides they want to move their WordPress,
    442. They move the folder to a new URL,
    553. Their admin page stops working, because it still had the old URL hard-coded.