Actions
Bug #5960
closed
isAuthorized is not unique enough when using uniqid
Description
When using dummy privacy rows uniqid is used to cache the results, but it's not unique enough. Generate a more unique id until "asset" column can be implemented, which will be improve the caching (cached by user id and asset).
Updated by krileon over 8 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Doesn't need to be unique. Just needs to be more specific. It should construct as follows.
OWNER_ID.TYPE.SUBTYPE.ITEM.RULE
This will ensure it's cached based off the dummy rows data properly. Caching is also already 2-stage. First cache by myId then by the privacy row. Examples as follows.
62.profile.tab.4.99
43.profile.1
81.profile.field.28.99
Actions