[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 westi):

 Replying to [comment:34 nbachiyski]:
 > I have a few questions:
 >   - Are orphaned terms causing trouble in other parts of WordPress? If
 yes, we should solve this at a higher level.
 >   - 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.
 >   - What is the root cause? Can we just fix it, fix all the sites, and
 not bother with adding more code here?

 Orphaned terms are possible to create in core WordPress too, we have some
 code which tries to help prevent orphans and loops but it isn't perfect.

 From what I recall there isn't a single root cause.

 There are other tickets open around improving the core code to prevent
 more loops/orphans but I'm not sure we will ever be able to 100% prevent
 them and we should code defensively for there existence IMHO.

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