Closed djtimca closed 3 years ago
The issue appears only to affect users who have restricted locations and where the location is disabled. If the location is enabled the error does not exist
Tracking back on this, do we really want to grant a restricted user access to a disabled location?
In my use case I have multiple restaurants with different owners being set up. When we set up their account we grant access to the location only. I want their location to remain disabled and not visible until they have completed setup of their menus etc and are ready to launch on the platform.
If I want to restrict their access to the platform I do it either through removing access to a specific location or by disabling their login altogether.
Each "location owner" though needs the ability to disable and reenable their location as required for their own operations.
You make a good point! I'll merge the PR.
Expected behavior: For a user with access to a single location they should be able to access the restaurant settings page (with appropriate permissions).
For a user with multiple assigned locations they should be able to access settings for all their assigned locations.
Actual behavior: Single location access users get the following error when they go to settings:
Users with multiple location access get a blank list when they access the Locations page.
Reproduce steps: Upgraded to version v3.0.4-beta.26 and this exists.
Version: v3.0.4-beta.26
Additional Information: Error from the system logs also appears: