WordPress importer struggles with large datasets. Once it crashes, there's no easy way to resume. Let's change that. High-level steps to get there: * https://github.com/WordPress/wordpress-importer/issues/228 * Streaming ID and author mapping (without accumulating global state or running table-wide UPDATE queries) * Save importer cursor, resume from the last stored cursor Related to https://github.com/WordPress/php-toolkit/issues/138
WordPress importer struggles with large datasets. Once it crashes, there's no easy way to resume. Let's change that.
High-level steps to get there:
Related to WordPress/php-toolkit#138