-
Notifications
You must be signed in to change notification settings - Fork 10
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
Support asset collections for filtering #12
Conversation
This allows to filter the assets through the use of asset collections. If the name of an asset collection matches a category in pixx.io, only the assets contained in that category (and it's sub-categories) are shown.
… for the category support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm the import via cli and the configuration works for the import works as documented.
However i can only see the collections in the Neos AssetSource and not the PixxIO asset source. This may be a problem of the Neos version i tested with. (currently 5.3, update to 7.3 is prepared)
Yes, as stated in the README with this PR: The pixx.io asset source declares itself read-only. Neos does not show asset
collections in the UI for read-only asset sources. This has been changed for
Neos 7.3.0 and up with https://github.com/neos/neos-development-collection/pull/3481
If you want to use this feature with older Neos versions, you can use the PR with
[cweagans/composer-patches](https://github.com/cweagans/composer-patches#readme)
or copy the adjusted template into your project and use `Views.yaml` to activate it. |
# Conflicts: # README.md
This provides a way to filter on the pixx.io side by the selected asset collection.
This allows to provide the category (folder) structure in pixx.io on the Neos side.
To support this, a CLI command is added to import (a configurable set of)
categories into Neos as asset collections.