Weekly migration project update

Just a quick update today, as I’ve been a little sick and stayed offline for a few days.

Per my timeline, I worked on a light component last week that focuses on the URL replacement part of a migration operation (e.g. from http://www.example.com to https://wp.example.com/wordpress). Hints were taken from the way search-and-replace was implemented in WP-CLI. My goal was to make this usable in whatever UI implementation is built later. I also need to get a grasp on how unit tests are actually done with core, because dependencies on functions like get_option() make systematic testing more difficult without an accessible database and tables.

In terms of what to expand on with the importer, an important question that remains is just how much should be moved with the importer.

At the moment, despite its deficiencies, its scope can be simply delineated: it moves content. Just content. Not plugins, not site options, not themes. If the importer were expanded to use WordPress’s XML-RPC API to transfer more — to copy over site options, to install plugins based on what was previously active — then it’s much harder to draw the line at what the importer will and will not do. I think this is an important decision question that would benefit from some community input.

This week, I’ll be coding more actively. To be done: a usable UI that can be used to test the work done thus far, and a fork of the existing importer plugin in which I will make my improvements.

#migration-portability, #weekly-update