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
When selecting the site/folder field for "file asset" in the content type properties, any attempt to save will not work and the field will revert back to "system host". This prevents users who do not have "all sites" permissions to add or edit content of this type.
Also, when a user of the above permissions attempts to filter the content search for the "file asset" type, they will be unable to view any content items.
This breaks the experience for use of file assets in many contexts for non "all sites" permissioned users.
Steps to Reproduce
Try to change the file asset site/folder field in the content properties to demo. See it reverts back to system host
Try to filter the content search to file as a limited user of only permissions for demo.dotcms.com (not all sites), see "file" is not available in the content search Please see screen recording here
Acceptance Criteria
File Assets should be visible if the user is permissioned to see them whether they are filtered in the content search, or a custom content tool.
The file asset content type should be able to have the site or folder field set to other hosts if desired, not default back after updating to system host.
dotCMS Version
Current/demo
Proposed Objective
Core Features
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered:
ian-b-cooper
changed the title
File Asset lockded site/folder field and Permissions Restriction
File Asset locked site/folder field and Permissions Restriction
Nov 21, 2024
Parent Issue
No response
Problem Statement
When selecting the site/folder field for "file asset" in the content type properties, any attempt to save will not work and the field will revert back to "system host". This prevents users who do not have "all sites" permissions to add or edit content of this type.
Also, when a user of the above permissions attempts to filter the content search for the "file asset" type, they will be unable to view any content items.
This breaks the experience for use of file assets in many contexts for non "all sites" permissioned users.
Steps to Reproduce
Please see screen recording here
Acceptance Criteria
File Assets should be visible if the user is permissioned to see them whether they are filtered in the content search, or a custom content tool.
The file asset content type should be able to have the site or folder field set to other hosts if desired, not default back after updating to system host.
dotCMS Version
Current/demo
Proposed Objective
Core Features
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: