Project

General

Profile

Actions

Feature proposal #4061

closed

Implement debug variable per action

Added by krileon over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
04 June 2013
Due date:
% Done:

100%

Estimated time:

Description

When enabled it outputs debugging results. For example tells you what conditional failed and the values it tried to match. It should also output the variables the trigger provided.

Actions #1

Updated by krileon over 11 years ago

A new "Log" page should be implemented in backend so this information can be logged to instead of dumped to avoid interrupting normal frontend workflows.

Actions #2

Updated by krileon over 11 years ago

Logging doesn't seam practical and could easily fill up quickly. Instead just do var_dumps.

Actions #3

Updated by krileon over 11 years ago

  • Status changed from Assigned to Rejected

Most triggers this will cause serious stopping issues and many it won't ever be seen.

Actions #4

Updated by krileon over 11 years ago

  • Status changed from Rejected to Assigned

Re-review possibility of this. Could add a parameter per action that when enabled will output the results of access check, conditional checks, exclude checks, etc..

Actions #5

Updated by krileon over 11 years ago

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

Enabling the debug parameter will debug the path to when the action is executed. It will not debug the individual actions. What this will tell you is if an access check failed, a conditional check failed, an exclude check failed, or if the action is missing a get method. In case of conditional check for example it'll tell you what action failed, what conditional failed, and what values it tried to match.

Actions #6

Updated by krileon over 11 years ago

  • Target version set to 5.0.0
Actions #7

Updated by krileon over 11 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF