Bug #6317
closed
fieldsFetch acting on wrong user object
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
Updated by krileon almost 8 years ago
Calling of _getTabFieldsDb with the viewing user object isn't always the case. So the proposed possible fix likely isn't viable. The trigger needs to send more information like $this or $this->_cbuser so the conditions can be done against the CBuser object and not the viewing user.
Updated by krileon almost 8 years ago
- Related to Bug #6318: onAfterFieldsFetch does not container enough information added
Updated by krileon almost 8 years ago
Just check if $fieldIdOrName is supplied and if it is then skip the fieldsFetch conditioning as we'll handle it on display.
Updated by krileon almost 8 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100