Bug #6318
closed
onAfterFieldsFetch does not container enough information
100%
Description
When onAfterFieldsFetch is fired the $user object is the object given to the _getTabFieldsDb function. The problem is if you're calling getFields then the user object is of the viewing user while the getFields object is $this->_cbuser. This means CB Conditional is being given the viewing user object instead of the displayed user object when testing conditions.
Including $this->_cbuser with the trigger would resolve this. onAfterTabsFetch will likely need the same fix.
Updated by krileon over 7 years ago
- Related to Bug #6317: fieldsFetch acting on wrong user object added
Updated by krileon over 7 years ago
- Status changed from Assigned to Rejected
- Target version deleted (
CB 2.1) - % Done changed from 0 to 100
getFields usage supplies $fieldIdOrName. No other usage does. This can be used to determine a getFields API call was made and then can be ignored in CB Conditional as needed (in this case we don't want to remove from the fields array, but instead remove at display time).