WordPress.org

Make WordPress Core

Opened 6 years ago

Last modified 8 months ago

#10762 assigned defect (bug)

Bulk editing creates invalid URIs

Reported by: hakre Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 2.8.4
Component: Quick/Bulk Edit Keywords: needs-patch
Focuses: Cc:

Description

They simply get too long for example if you move 999 posts to trash. It might be helpfull to switch to the post form method.

Change History (20)

comment:1 @scribu6 years ago

Never did understand why a GET request is used in this case. Should use POST.

comment:2 @azaozz6 years ago

Bulk Edit submits the main form on the page which uses GET. It could be refactored to use POST but that's not a trivial task.

comment:3 follow-up: @hakre5 years ago

For me it seems that replacing $_GET with $_REQUEST is pretty trivial. It might not be trivial to test if that's working then.

comment:4 @hakre5 years ago

Related: #11114

comment:5 @hakre5 years ago

Related: #10360

comment:6 in reply to: ↑ 3 @nacin5 years ago

  • Milestone changed from 2.9 to 3.0

Replying to hakre:

For me it seems that replacing $_GET with $_REQUEST is pretty trivial. It might not be trivial to test if that's working then.

If you bulk-delete posts, the IDs are passed back to the form, that way the undo button can be generated. So hidden fields would also need to be created to ensure that the URI can't get too long.

It's a complicated process to go through however many forms use bulk actions and redo all of the add_query_arg code and such. Definitely quite the task.

comment:7 @dd325 years ago

  • Milestone changed from 3.0 to Future Release

As this isnt a Regression from a previous version, and there is no patch, I'm moving to Future Release.

comment:8 @scribu5 years ago

  • Keywords gsoc added
  • Owner set to scribu
  • Status changed from new to assigned

comment:10 @voyagerfan57615 years ago

  • Cc WordPress@… added

comment:11 @scribu5 years ago

  • Milestone changed from Future Release to 3.1
  • Resolution set to fixed
  • Status changed from assigned to closed

comment:12 @nacin4 years ago

  • Component changed from Accessibility to Administration
  • Keywords gsoc removed
  • Milestone changed from 3.1 to Future Release
  • Resolution fixed deleted
  • Status changed from closed to reopened

#16335. We'll need to fix this in conjunction with ajax redux.

comment:13 @scribu3 years ago

  • Owner scribu deleted
  • Status changed from reopened to assigned

comment:14 @scribu2 years ago

#22062 was marked as a duplicate.

comment:15 @scribu2 years ago

#22062 was marked as a duplicate.

comment:16 @ocean9023 months ago

#24323 was marked as a duplicate.

comment:17 @ocean9014 months ago

  • Component changed from Administration to Quick/Bulk Edit

comment:18 @ocean9011 months ago

#28192 was marked as a duplicate.

comment:19 @ocean908 months ago

#29049 was marked as a duplicate.

comment:20 @SergeyBiryukov8 months ago

#29116 was marked as a duplicate.

Note: See TracTickets for help on using tickets.