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 configuring a collection with DRM and configuring it so that you do not have to accept the terms to view the item summary (only when viewing the attachment), when you go to view the item summary from a search results, it prompts you for DRM terms.
This is the option on the DRM control:
To Reproduce
Steps to reproduce the behavior:
Set up the DRM control so that the above option is not selected (don’t have to accept rights at an item level)
Create a new item in the DRM collection (or you can use an existing one)
From the Search page, click on the DRM item to open the summary page - it shows the Acceptance dialog.
Expected behavior
It should open the summary page without showing the acceptance dialog.
It should only show the Acceptance dialog when you try to view an attachment.
Screenshots
If applicable, add screenshots to help explain your problem.
Stacktrace
If applicable, a stacktrace to help explain your problem.
Platform:
OpenEquella Version: [e.g. 6.5, 6.6]
OS: [e.g. Windows 10, MacOS 10.13]
Browser [e.g. Chrome, Firefox]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
This only happens in new UI
When configuring a collection with DRM and configuring it so that you do not have to accept the terms to view the item summary (only when viewing the attachment), when you go to view the item summary from a search results, it prompts you for DRM terms.
This is the option on the DRM control:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should open the summary page without showing the acceptance dialog.
It should only show the Acceptance dialog when you try to view an attachment.
Screenshots
If applicable, add screenshots to help explain your problem.
Stacktrace
If applicable, a stacktrace to help explain your problem.
Platform:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: