Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-4956

Contact permissions have inconsistent associations

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.8.0
    • Fix Version/s: 5.8.1
    • Component/s: None
    • Labels:
      None

      Description

      The way contact permission are set and evaluated seems inconsistent. For example Contacts::hasPermission() expects that the contact's client_id be set in the contact_permissions table, while delete() expects the column to be null. And the upgrade script does not set any client_id at all. Also ManagedAccounts::getAccounts seems to expect the column to be null for non account managers.

      I think the correct thing to do is to make a script to set the column equal to the contact's client id if the column is null and change the column to be non-null. Then update all other area's to expect the column to be non-null

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            jonathan Jonathan Reissmueller
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              30/Aug/23

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 25 minutes
              25m

                Agile