You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Favorites page inconsistently handles files and folders compared to other areas, such as Personal Files. The primary issue is the inability to edit permissions, set aspects, or manage rules for nodes within Favorites. However, editing the node's name and description remains possible, suggesting this limitation may be unintended. Additionally, a terminating separator line in the context menu implies missing expected options, further indicating a potential oversight.
Environment
ACA version: 4.4.1 (Probably applicable to all versions)
ACS version: 6.7.1
To Reproduce
Mark a node as a favorite.
Navigate to the Favorites page.
Right-click on the node.
Expected behavior
The interface should provide consistent functionality, irrespective of whether a node is accessed from the Favorites page or elsewhere.
Additional context
This issue likely stems from the Favorites page utilizing specific API calls that lack comprehensive node information, such as editable permissions and other properties. A possible solution could involve modifying the Favorites API or, preferably, retrieving only the node reference from the Favorites API and leveraging the node API for detailed information.
The text was updated successfully, but these errors were encountered:
Describe the bug
The Favorites page inconsistently handles files and folders compared to other areas, such as Personal Files. The primary issue is the inability to edit permissions, set aspects, or manage rules for nodes within Favorites. However, editing the node's name and description remains possible, suggesting this limitation may be unintended. Additionally, a terminating separator line in the context menu implies missing expected options, further indicating a potential oversight.
Environment
To Reproduce
Expected behavior
The interface should provide consistent functionality, irrespective of whether a node is accessed from the Favorites page or elsewhere.
Additional context
This issue likely stems from the Favorites page utilizing specific API calls that lack comprehensive node information, such as editable permissions and other properties. A possible solution could involve modifying the Favorites API or, preferably, retrieving only the node reference from the Favorites API and leveraging the node API for detailed information.
The text was updated successfully, but these errors were encountered: