«Read only» visibility for Seo Pro fieldtype is not working / a.k.a hide Seo Pro fieldtype for editors
helloDanuk opened this issue · comments
Use case:
I have the following use case: SEO Pro is set up for all collections and entries. "Editors" do not need to make any changes in the SEO Pro fieldtype. Everything runs automatically, individual fields (such as descriptions) are inherited from another text field in the collection blueprint.
Problem:
So that nothing gets mixed up, editors should not be able to make any content changes in the Seo Pro fieldtype, but it would be practical for super users to have access to the fields.
The most obvious solution would be an option to show/hide the Seo Pro fieldtype in the permissions for the individual roles. But that is not possible?
Further I thought as a workaround, I could set the Seo Pro fieldtype to "read only", so that at least super users can see what the settings are per collection and where there are individual variations set up per entry. When changes are made, they would have to temporarily remove the "read only" status. But the "read only" setting has no effect? Changes are still applied and saved.
Only the "Hidden" option hides the Seo Pro fieldtype. However, this is not ideal for super users, as they can no longer see what is set where.
I am missing something?
Environment
Application Name: SpielRaum CMS
Laravel Version: 10.43.0
PHP Version: 8.2.6
Composer Version: 2.6.2
Environment: local
Debug Mode: ENABLED
URL: spielraum-tmp.test
Maintenance Mode: OFF
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: sendmail
Queue: sync
Session: file
Statamic
Addons: 2
Antlers: runtime
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.48.0 PRO
Statamic Addons
statamic/seo-pro: 5.4.1
swiftmade/statamic-clear-assets: 2.0.1