Project

General

Profile

Actions
Copy link

Bug #6317

closed

fieldsFetch acting on wrong user object

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

Status:
Closed
Priority:
Urgent
Assignee:
krileon
Target version:
5.0.0
Start date:
30 November 2016
Due date:
% Done:

100%

Estimated time:

Description

When getFields is called it triggers onAfterFieldsFetch with the viewing user object instead of the CBuser user object. This results in the conditions being applied to the wrong user. The conditioning in fieldsFetch can PROBABLY just be applied to SAVE states only. For example during profile edit or registration save. The same will have to apply to tabsFetch most likely as well.

https://www.joomlapolis.com/forum/255-developer-members-support/235347-substitutions-question#288391

Related issues 1 (0 open — 1 closed)

Related to CB - Bug #6318: onAfterFieldsFetch does not container enough informationRejectedkrileon30 November 2016

Actions
Actions
Copy link

Also available in: Atom PDF