Project

General

Profile

Actions
Copy link

Bug #4233

closed

Fields not accessible can't be conditioned

Bug #4233: Fields not accessible can't be conditioned

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

Status:
Closed
Priority:
Normal
Assignee:
krileon
Target version:
3.0.11
Start date:
06 September 2013
Due date:
% Done:

100%

Estimated time:

Description

If you condition off a field that is on a tab accessible only to Special then the value will always be NULL. This is because the POST value is NULL and the getFields value is NULL. It should fallback to grabbing its value from user object if all of the above result in null.

Actions
Copy link

Also available in: PDF Atom