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
{{ message }}
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
Not sure if this is intended, if so, consider this a super low-priority feature request...
A non-owner can not turn fields on/off in the content type entries listing.
I think it's valuable to have the ability for non-owners to do this, but I also understand why it's locked down, due to it effecting all users' views.
Maybe determine an easy way to add that to the permission system for groups?
A good use case occurred when I was demonstrating Webhook. They were logged into the CMS with Editor perms, and got excited when they saw they could add/remove display fields from the listings -- until they couldn't (I then gave them owner privs.) The thought was that it would be valuable in combination with search to do some quick "at a glance" audits (for SEO, unpublished items, etc.)
Considering the limited width for item listings, I thought it was a decent enough idea.
The text was updated successfully, but these errors were encountered:
Problem: Display fields are saved to the content-type which is only writable by owners.
Solution: Use display fields on content-type as the default. Override as user level. Save to settings/userprefs/[username]/contentTypes/[contentTypeName]/.
New resulting problem: No UI for setting default display fields.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not sure if this is intended, if so, consider this a super low-priority feature request...
A non-owner can not turn fields on/off in the content type entries listing.
I think it's valuable to have the ability for non-owners to do this, but I also understand why it's locked down, due to it effecting all users' views.
Maybe determine an easy way to add that to the permission system for groups?
A good use case occurred when I was demonstrating Webhook. They were logged into the CMS with Editor perms, and got excited when they saw they could add/remove display fields from the listings -- until they couldn't (I then gave them owner privs.) The thought was that it would be valuable in combination with search to do some quick "at a glance" audits (for SEO, unpublished items, etc.)
Considering the limited width for item listings, I thought it was a decent enough idea.
The text was updated successfully, but these errors were encountered: