Feature proposal #7139
closed
Redesign trigger usage
Description
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.
return 'test';
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.
This will make it easier to add/remove positions without completely breaking the variable order.
Updated by krileon over 6 years ago
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.
Updated by krileon about 1 year ago
- Status changed from Assigned to Closed
- % Done changed from 50 to 100
Layout triggers (basically most beginning with "onDisplay") now have their layout data compressed into a single $layout array. This matches how layout data is used in template files themselves and makes it easier to add/remove additional layout data without breaking trigger function binding. Also avoids trigger functions having a dozen+ parameters.