Project

General

Profile

Actions

Bug #5094

closed

Field conditions fail if the field it's conditioning off of isn't available

Added by krileon over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
19 February 2015
Due date:
% Done:

100%

Estimated time:

Description

If a field is conditioned off another field that isn't available (e.g. Access permission) then the condition always fails. It should pull the initial PHP value, send it to jQuery, see that the field can't be found, and just static stay with the PHP value. This way the condition would just act like a Custom > Value usage.

Actions #1

Updated by krileon over 7 years ago

  • Target version changed from 4.0.5 to 4.0.6
Actions #2

Updated by krileon over 6 years ago

PHP is passing fine now due to rewrite of getFieldValue, but the JS isn't firing its condition.

Actions #3

Updated by krileon over 6 years ago

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

This is due to static condition fallback in JS not taking affect due to being at the wrong location.

Actions #4

Updated by krileon over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF