#10012 closed enhancement (fixed)
No custom taxonomy import, nor export
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 2.9 |
| Component: | Export | Version: | |
| Severity: | minor | Keywords: | needs-testing, has-patch, import, export, taxonomy |
| Cc: |
Description
Although since 2.3 it's possible to use custom taxonomies, there seems absolutely no support for that in the export, nor in the import routines.
In the mean time I'm working on an importer, that does this. When I'm finished, and it works as good as expected I'll contribute it.
Attachments (1)
Change History (11)
- Keywords needs-patch added
- Priority changed from normal to low
- Severity changed from normal to minor
comment:3
in reply to:
↑ description
tntc1978 — 4 years ago
With use-cases like these, it seems that this feature should be essential in an export and import.
I'm working on a new site that uses custom taxonomies and realized that there is no import/export support. I'm automating the import of posts and it would be nice to have this feature.
@djzone - any progress on an importer?
comment:5
chrisscott — 4 years ago
- Keywords needs-testing has-patch added; needs-patch removed
comment:6
chrisscott — 4 years ago
- Keywords changed from needs-testing, has-patch import, export, taxonomy to needs-testing, has-patch, import, export, taxonomy
Shouldn't wxr_tag_description() be wxr_term_description()? Other than that the patch looks good to me. We'll need to decide if this can go into 2.9 during our current soft feature freeze.
chrisscott — 4 years ago
comment:8
chrisscott — 4 years ago
Thanks, Ryan. Good catch, new patch attached.
- Milestone changed from Future Release to 2.9
- Resolution set to fixed
- Status changed from new to closed
This is not a minor problem.