Context Navigation

← Previous Change
Ticket History
Next Change →

Changes between Initial Version and Version 1 of Ticket #55135

Timestamp:

02/10/2022 10:58:10 AM (4 years ago)

Author:

SergeyBiryukov

Comment:

Hi there, welcome back to WordPress Trac! Thanks for the ticket.

Using absolute URLs in the database is a design decision, see Absolute versus relative URLs in the core handbook.

When migrating to another domain, it's often easier to just replace all the site URLs with WP-CLI or other tools like the Database Search and Replace script. With relative URLs, it's true that no replacement is needed in this case, but it gets significantly harder to reliably move the site to a different path.

Apart from #17048, this was also previously discussed or mentioned in #29273, #32639, #34609, #34741, #37723, and #40336. That said, it looks like using relative URLs in the export file specifically has not been discussed before, so I think we can use this ticket to investigate that.

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #55135
- Property Component Import → Export

Ticket #55135 – Description

-              initial
+              v1
 The hard-coded links require post-processing the XML file for the content to be portable across domains and environments (e.g., development, staging, and production).
+Ideally, media URLs in the export file would be relative to the WordPress root, such as described in the following issue from 11 years ago:
+https://core.trac.wordpress.org/ticket/17048
+Ideally, media URLs in the export file would be relative to the WordPress root, such as described in the following issue from 11 years ago: #17048.

Make WordPress Core

Context Navigation

Changes between Initial Version and Version 1 of Ticket #55135

Legend:

Ticket #55135

Ticket #55135 – Description