Project

General

Profile

Actions

Feature proposal #7140

closed

Redesign trigger usage

Feature proposal #7140: Redesign trigger usage

Added by krileon over 8 years ago. Updated about 20 hours ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
08 May 2018
Due date:
% Done:

100%

Estimated time:

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.

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.

Updated by krileon 30 days ago Actions #1

  • Target version changed from 5.0.0 to 4.0.0

Updated by krileon 15 days ago Actions #2

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

All $return handling has been removed. Direct responses from triggers will be treated as return output instead.

Updated by krileon about 20 hours ago Actions #3

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom