[wp-trac] [WordPress Trac] #22435: Export API

[WordPress Trac]

#22435: Export API
------------------------------------+------------------------------
 Reporter:  nbachiyski              |       Owner:
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Export                  |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  dev-feedback has-patch  |
------------------------------------+------------------------------

Comment (by dllh):

 Replying to [comment:34 nbachiyski]:

 >   - Are orphaned terms causing trouble in other parts of WordPress? If
 yes, we should solve this at a higher level.

 I'm not aware of any other places where it causes trouble; I've only ever
 seen it affect exports. But I can't say that it's not causing issues
 elsewhere.

 >   - Is this problem known outside of WordPress.com? If not, can we just
 add a filter/action in the export and deal with this locally on
 WordPress.com, instead of adding more code and complexity for everybody.

 Seems like it would affect any WP install, but then we do have some weird
 tax stuff going on on wpcom. I've never managed to reproduce the natural
 creation of a tax loop (that is, without hacking one in), so my impression
 is that these are mostly legacy issues. Maybe it's possible to import
 incorrectly parented terms, but I haven't repro'd such a case.

 >   - What is the root cause? Can we just fix it, fix all the sites, and
 not bother with adding more code here?

 This probably isn't practical for wpcom. If we're reluctant to add tax
 loop stuff in core, I'd be cool with just adding an action we could fire
 instead and hook onto that on wpcom.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/22435#comment:35>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software