WordPress.org

Make WordPress Core

Changes between Initial Version and Version 4 of Ticket #15197


Ignore:
Timestamp:
10/24/10 11:00:19 (3 years ago)
Author:
duck_
Comment:

New import patch coming soon with WXR 1.0 author fix and a few other things.

The current todo:

  • Give better feedback to the user at the end of import
  • Re-implement export filtering
  • Double check for undefined variables/indexes on WXR 1.0 import

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15197

    • Property Cc westi beau@… added
  • Ticket #15197 – Description

    initial v4  
    2727=== Backwards Compatibility === 
    2828The main problem for now is ensuring backwards compatibility with WXR 1.0 files. That said, no major faults ''should'' occur when importing a 1.0 file. Excluding all the problems you will come across already in an export/import in 3.0.1: 
    29  * No author import (the current importer takes author data from each post)[[BR]]'''Possible solution:''' if we get an empty author array then loop through posts grabbing unique authors and offering to map them (but not to import) 
    30  * I think (not tested properly yet) that all term menu items will be skipped due to missing term_id XML tags so no way of mapping old ID to new[[BR]]'''Possible solution:''' off the top of my head, maybe slugs instead of IDs for processed_terms mapping (?)   
     29 * No author import (the current importer takes author data from each post)[[BR]]'''SOLVED:''' if we get an empty author array then loop through posts grabbing unique authors and offering to map them (but not to import) 
     30 * ~~All term menu items will be skipped due to missing term_id XML tags '''Possible solution:''' slugs instead of IDs for processed_terms mapping?~~ In fact, as far as I can see, filling imported menus is actually impossible with WXR 1.0 since the file doesn't contain custom terms for post items, see #13453 and #14306, so we don't know which menu to assign the menu items to 
    3131 * Probably some indexes and vars which need to be checked with isset and fallback provided (for when the XML tag doesn't exist in 1.0 files)  
    3232 * ... and possibly more with further testing 
     
    3939 * Makes reliable importing of nav menus harder (worse UX when importer is creating half made menus) 
    4040 
    41 Moving forward I am currently imagining some sort of grid of post types selectable by checkbox. Each post type lists its taxonomies below, these are 
    42 only activated/recognised if the post type is selected. But what filters to include and how to show them are probably for another ticket. 
     41~~Moving forward I am currently imagining some sort of grid of post types selectable by checkbox. Each post type lists its taxonomies below, these are only activated/recognised if the post type is selected. But what filters to include and how to show them are probably for another ticket.~~ 
     42 
     43See [comment:ticket:15197:3 nacin's comment] and [attachment:ticket:15197:15197.filtering.png mockup] for the current plan for export filtering. 
    4344 
    4445=== Other ===