Project

General

Profile

Actions

Bug #8232

closed

getField API passing wrong user object to _getTabFieldsDb

Added by krileon over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
11 November 2020
Due date:
% Done:

100%

Estimated time:

Description

getField is passing the viewing user object to _getTabFieldsDb which is exclusively used in the onAfterFieldsFetch trigger (has no impact on _getTabFieldsDb functionality, which is correct). This is causing unexpected behavior in plugins since onAfterFieldsFetch is being used with the understanding that $user is the user that's being fetched.

Actions #1

Updated by krileon over 3 years ago

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

Fixed in MR !1594

Actions #2

Updated by beat over 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF