Feature proposal #7140
Redesign trigger usage
Currently various triggers send by reference variables for adding content to specific locations. Get rid of this behavior entirely and simply handle it in the return. Example as follows.
A plugin doing that on a trigger would insert to default position.
return array( 'buttons' => 'test' );
A plugin doing that on a trigger would insert to the buttons position.
For edit views use an integration_edit template file that can loop array returns into field rows. This prevents the integrations having to supply any HTML. They'd supply the label and the input and that's all they'd have to do.
This will make it easier to add/remove positions without completely breaking the variable order.