[wp-trac] [WordPress Trac] #60375: Site Transfer Protocol

[WordPress Trac]

#60375: Site Transfer Protocol
-------------------------+------------------------------
 Reporter:  zieladam     |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Import       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by dmsnell):

 > Unlike WXR imports

 Lately I've been thinking that we could augment WXR since it's inherently
 expandable, to communicate much of the extra site meta. In fact, existing
 imports would/should ignore those sections, but transfers could use the
 information to aid in the import.

 > Communicate source and destination site domains/base URLs

 One challenge in recording source and destination is that either can
 disappear. If we normalize all deployment-related information to the
 Playground and its URLs, then presumably we could export from any site,
 and that same export file could be imported into any other deployment,
 regardless of where it originated or where it's bound.

 This could also easy the identification of assets within the database
 since there would be a common Playground prefix.

 > Communicate wp-config.php settings, including things like WP_SITEURL and
 plugins directory, theme directory, content directory, memory limits, and
 other settings.

 Extending the previous point, a transform to the Playground as an
 intermediary would give us the chance to not only record those options
 which are specifically called out on the source site, but potentially
 other available settings so that we can ensure proper reception.

 Consider if we normalize to a Playground environment where every custom
 setting is adjusted. Someone could load that export file into the
 Playground and ensure it will work wherever it's going. For example, maybe
 there's a custom location for plugins; if the source site is hard-coding
 values then it might break on import. This preview step would provide an
 opportunity to catch that error.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60375#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform