WordPress.org

Make WordPress Core

Opened 2 years ago

Last modified 22 months ago

#19307 new enhancement

Need ability to export "All content" but limited to date range

Reported by: lloydbudd Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 3.1
Component: Export Keywords: needs-patch regression westi-likes 3.4-early
Focuses: Cc:

Description

Need ability to export "All content" but limited to date range

ENV

WP 3.3-beta3-19254 (trunk r19367)

Additional Details

For a larger site is a common scenario to need to export all content, but because of resource limitations or time constraints it cannot be done in a single export.

Exporting individual post types is not a work around, further you lose attachments on posts when exporting just "posts", and that breaks features including Featured Images.

Also Consider

Another common scenario for media and enterprise customer is wanting to export a period of time to further analysis that content, or stage it in their development environment for debugging an issue, or developing new designs and features.

Attachments (1)

19307.diff (3.7 KB) - added by sorich87 2 years ago.

Download all attachments as: .zip

Change History (21)

comment:1 lloydbudd2 years ago

  • Keywords needs-patch added

comment:2 jane2 years ago

Labeling this regression implies that this worked in 3.2. I don't see 'export "All content" but limited to date range' as an option in 3.2. Am I missing something? People have hit limits for longer than 3.3, I've replied to a number of support requests that end in 'raise the limit'. Please specify how this is a regression.

comment:3 duck_2 years ago

  • Version changed from 3.3 to 3.1

#15197. Filtering by date range for all content was available in 3.0 only and not before I think.

comment:4 jane2 years ago

In that case in sort of is and sort of isn't a regression. I don't think it should be a blocker in 3.3 if it has been absent since 3.1.

comment:5 lloydbudd2 years ago

Thanks for the clarifications @jane & @duck_ . I think what will make this painful is one WordPress host (WordPress.com !) falling way behind in importer/exporter until just now -- they were still using 3.0s code!

comment:6 batmoo2 years ago

  • Cc batmoo@… added

comment:7 follow-up: ocean902 years ago

  • Keywords regression removed
  • Milestone changed from 3.3 to Future Release
  • Severity changed from major to normal
  • Type changed from defect (bug) to enhancement

2.9: http://cl.ly/ByLv

3.0: http://cl.ly/ByjF

And since 3.1 the current one, so no regression here.

comment:8 in reply to: ↑ 7 lloydbudd2 years ago

  • Keywords regression added
  • Milestone changed from Future Release to 3.3
  • Severity changed from normal to major

Replying to ocean90:

2.9: http://cl.ly/ByLv

3.0: http://cl.ly/ByjF

And since 3.1 the current one, so no regression here.

@ocean90 sorry, I don't understand your update. "3.0: http://cl.ly/ByjF " shows the desired behavior. Reverting changes to ticket.

comment:9 follow-up: nacin2 years ago

  • Keywords regression removed
  • Milestone changed from 3.3 to Future Release
  • Priority changed from normal to low
  • Severity changed from major to normal

This is not a recent regression, and while it may stymy someone's established workflow, the export can be broken up in other ways. The enhancements here far outweigh the single drawback. Because this was a design decision to upgrade the UI, I'm also removing the regression tag. Punting.

comment:10 Viper007Bond2 years ago

#18694 may prove helpful in implementing this functionality.

Last edited 2 years ago by Viper007Bond (previous) (diff)

comment:11 jane2 years ago

Lloyd -- the behavior was changed intentionally in 3.1. So it wasn't a regression from 3.2 to 3.3. Yes, it should be fixed, but it's not going to happen in 3.3 with RC around the corner. At this point, only security issues could get in getting being raised this late in the game.

comment:12 lloydbudd2 years ago

Hi @jane, thanks for the detailed explanation. That helps.

comment:13 in reply to: ↑ 9 westi2 years ago

  • Keywords regression westi-likes 3.4-early added
  • Priority changed from low to high

Replying to nacin:

This is not a recent regression, and while it may stymy someone's established workflow, the export can be broken up in other ways. The enhancements here far outweigh the single drawback. Because this was a design decision to upgrade the UI, I'm also removing the regression tag. Punting.

While it should be punted from 3.3 it is a regression.

It makes no sense to a user to not get the attachments in the export file when exporting a range of posts.

comment:14 ddeconin2 years ago

I'm having the same issue. Its been since 2.9 that I needed to perform this operation, but now I really need it and I'm stuck. So its not an 'enhancement' to me.

comment:15 jane2 years ago

I don't think anyone is arguing against wanting the functionality, @ddeconin. The ticket was created too late in the 3.3 cycle for it to be included. Someone just needs to write a decent patch for this. If you have the ability, please consider contributing the code (vs just telling us you want the feature). Thanks.

comment:16 jane2 years ago

  • Priority changed from high to normal

sorich872 years ago

comment:17 follow-up: sorich872 years ago

This patch adds the date fields when "All content" is checked.

Should the fix for the attachments bug (the bug westi mentioned in a comment above) be included here? or another ticket created for that?

comment:18 in reply to: ↑ 17 duck_2 years ago

Replying to sorich87:

Should the fix for the attachments bug (the bug westi mentioned in a comment above) be included here? or another ticket created for that?

#17379

comment:19 jtsternberg2 years ago

  • Cc justin@… added

comment:20 hd-J22 months ago

  • Cc jeremy@… added
Note: See TracTickets for help on using tickets.