Project

General

Profile

Actions

Bug #6318

closed

onAfterFieldsFetch does not container enough information

Added by krileon almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
High
Assignee:
Target version:
-
Start date:
30 November 2016
Due date:
% Done:

100%

Estimated time:

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.


Related issues 1 (0 open1 closed)

Related to CB Conditional - Bug #6317: fieldsFetch acting on wrong user objectClosedkrileon30 November 2016

Actions
Actions

Also available in: Atom PDF