Permit custom field elements in left column of Quick Edit

[danielbachhuber]

Quick Edit supports adding custom fields via the quick_edit_custom_box action. Due to the two-column layout and where the action is called, it isn't easily possible to add your custom field in the left column of Quick Edit — only the right column.

If the design of Quick Edit is established indefinitely, it would be nice to have an additional action to place custom field elements in the left column.

[danielbachhuber]

For reference, ​here was my immediate "fix". I'll upload a patch with my proposal.

[danielbachhuber]

Add "after" actions for each of Quick Edit's columns

[DrewAPicture]

Instead of introducing what appears to be 6 new hooks, what about introducing 2 new hooks with a context parameter for left, center, or right. Even better, we could just introduce a single new hook, passing both a $bulk and context parameter.

Regardless, whatever we end up with will need ​hook docs.

[DrewAPicture]

Single inline_edit_after_column hook + docs

[DrewAPicture]

26982.diff​ combines the new hooks into a single a new hook with a $context parameter and $bulk. Not sure if using a boolean in this way is really recommended but it could work. Also adds hook docs.

[nacin]

The templating of Quick Edit needs an overhaul at some point down the line. Additional hooks, especially one wedded to the idea of "columns" (which, for responsive situations, is different), is probably gonna make it tougher to improve Quick Edit, both from the technical perspective (how we template it) and also how it looks and works (it could benefit from an update). (The next step, if I had to guess, is Underscore templates and Backbone.)

I'm not quite saying wontfix, I'm just saying we've never had very good luck when we've taken a giant block of HTML and loaded it up with a ton of actions. It usually bites us really hard later. Honestly, that JS hack doesn't bother me all that much. After all, this is a JS-driven feature.

[danielbachhuber]

I'm fine with wontfix for now then. The JS hack seems to work well-enough, and I agree that adding more actions isn't the ideal way to go about it.