Context Navigation

← Previous Ticket
Next Ticket →

#10012 closed enhancement (fixed)

No custom taxonomy import, nor export

Reported by:	djzone	Owned by:
Priority:	low	Milestone:	2.9
Component:	Export	Version:
Severity:	minor	Keywords:	needs-testing, has-patch, import, export, taxonomy
Cc:		Focuses:

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)

custom_taxonomy_export.patch (4.7 KB ) - added by chrisscott 17 years ago.

Download all attachments as: .zip

Change History (11)

#1 @Denis-de-Bernardy
17 years ago

Keywords needs-patch added
Priority normal → low
Severity normal → minor

#2 @jgoodwin
17 years ago

This is not a minor problem.

#3 in reply to: ↑ description @tntc1978
17 years ago

With use-cases like these, it seems that this feature should be essential in an export and import.

#4 @emartin24
17 years ago

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?

#5 @chrisscott
17 years ago

Keywords needs-testing has-patch added; needs-patch removed

See the attached patch. This adds a new element in the export, <wp:term>, as well as handling for it on the WordPress importer.

#6 @chrisscott
17 years ago

Keywords needs-testing, has-patch import, export, taxonomy → needs-testing, has-patch, import, export, taxonomy

#7 @ryan
17 years ago

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.