-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move ignored columns to the registry? #121
Comments
@gforcada I agree, |
We have the same feature request. |
@spereverde For Plone 6, currently use the master branch of each package. (You can always check in https://github.com/plone/buildout.coredev/blob/6.0/sources.cfg to see which branch of each package is officially part of Plone 6.) It can probably go either in this package or in CMFPlone, whichever is easier. Well, it probably should go in CMFPlone, since it could be used by volto as well, and this package is part of the classic UI. At this point it probably should not be merged until after the final release of Plone 6 (which I think is quite soon), since it is a new feature. |
Maybe Indeed not right now please. ;-) |
If ok for everyone, we'll make a PR for ignored_columns and ignored_indexes here : https://github.com/plone/plone.base/blob/main/src/plone/base/interfaces/controlpanel.py - class ISiteSchema |
Seems a fine place at first glance. |
On https://github.com/plone/plone.app.content/blob/master/plone/app/content/browser/contents/__init__.py in
FolderContentsView
class there is aignored_columns
method with a static list of catalog columns that are to be hidden from thefolder_contents
view.If someone, say me :-), wants to have any of those columns available the only way to do so is either fork p.a.content or override that method.
Wouldn't make sense to move this configuration, and probably others, in a plone.app.registry key so it would be a matter of changing some settings?
Is there any strong opinion against it?
The text was updated successfully, but these errors were encountered: