-
Notifications
You must be signed in to change notification settings - Fork 2
IBX-9762: Added default sharable content groups #216
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
Conversation
|
Thanks for contribution! 🎉 To test the changes please execute: before executing the recipes. |
adamwojs
left a comment
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.
Currently products are not supported.
|
@adamwojs , |
|
Reopend as there was a need to disable tags content types that are in Content group. |
c7b48ab to
78bf583
Compare
| @@ -0,0 +1,9 @@ | |||
| ibexa: | |||
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.
For v5, shoudn't it be part of the recipes for ibexa/headless?
It's not an optional package for v5.
I'm thinking about the update procedure - right now we recommend updating the packages and the recipes for the "meta package" only (https://doc.ibexa.co/en/5.0/update_and_migration/from_5.0/update_from_5.0/)
I'd like to avoid listing every package separately on that page
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.
This should be auto fetched and updated when require on ibexa/share is done. Routes are also grouped per package and they work as intended.
But maybe you are right, and there could be potential issues between 5.0 and 5.0.1, I will move it then, just to be safe.
78bf583 to
08a05bf
Compare
|



Related PRs:
Description:
For QA:
Documentation: