Opened 15 years ago
Closed 10 days ago
#12578 closed enhancement (reported-upstream)
import from movable type doesn't import tags or basename
Reported by: | stevecrozz | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0 |
Component: | Import | Keywords: | needs-refresh |
Focuses: | Cc: |
Description
The current movable type import script doesn't import tags from movable type and it doesn't import the basename (movable type's version of the post_name, which is necessary for a seemless transition). Adding support for importing these two important bits is not terribly difficult and I'm working on improving the import script to aid in my own upcoming migration. I'll attach a patch against the trunk.
Attachments (2)
Change History (11)
#2
@
15 years ago
- Keywords import movable type tags post_name removed
- Milestone changed from Unassigned to 3.1
- Owner set to nacin
- Status changed from new to assigned
basename in #11422.
As discussed in IRC I think we need to come up with a better way to break up the tags. Or just accept the edge cases and go with it as is.
#7
@
10 years ago
- Keywords needs-refresh added; has-patch removed
As movable type is no longer in core, the patch will need to be refreshed
#9
@
10 days ago
- Keywords wporg-importer removed
- Resolution set to reported-upstream
- Status changed from assigned to closed
The Moveable Type importer now lives on GitHub.
If anyone is still experiencing this issue, please open an issue upstream so it can be addressed appropriately.
related excerpt from a movable type export