Opened 9 years ago
Last modified 4 years ago
#36340 new enhancement
Other options ignored when using a custom post type with export_wp()
Reported by: | theMikeD | Owned by: | |
---|---|---|---|
Milestone: | Future Release | Priority: | normal |
Severity: | normal | Version: | |
Component: | Export | Keywords: | needs-patch |
Focuses: | Cc: |
Description (last modified by )
While writing the improved docblock for export_wp()
, I noticed something that may be an issue when a custom post type is supplied.
For the built-in post types you can filter the exported content by start date, end date and/or author. But not with a custom post type: with them it's everything. Is this by design?
The fix could be to modify line 113 to include the custom post type option because by that point we know that it's both valid and can_export
is true thanks to the stuff starting on line 88.
I don't use this code myself but it did jump out at me. Thoughts?
Change History (3)
Note: See
TracTickets for help on using
tickets.
The UI on the export screen doesn't allow filtering when exporting just an individual custom post type or when exporting all content, so this is just going to occur on direct calls to the
export_wp()
function itself.The documentation for the function arguments of
author
,start_date
andend_date
each say:Given all of that, I think this is an enhancement and not a bug, since it's a documented design.