-
Notifications
You must be signed in to change notification settings - Fork 81
[Collaboration] Added doc for latest changes #2965
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
Changes from all commits
307050f
c2ffbc7
83da25f
2b31cda
4e18cd7
e6ae7e6
58e8739
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -166,8 +166,60 @@ | |||||
|
|
||||||
| The following setting is available: | ||||||
|
|
||||||
| - `content_type_groups` – defines groups of content types for which the **Share** button is displayed (it can still be disabled for specific content types within these groups) | ||||||
| - `content_type_groups` – defines groups of content types for which the **Share** button is displayed (it can still be disabled for specific content types within these groups by using the `excluded_content_types` setting) | ||||||
|
|
||||||
| In the example confugiration above, the **Share** button is displayed for any content that belongs to the `Content` group, except for `tag` and `product_category_tag` content types. | ||||||
| In the example configuration above, the **Share** button is displayed for any content that belongs to the `Content` group, except for `tag` and `product_category_tag` content types. | ||||||
|
|
||||||
| You can also control which user content types can use the feature through the `ibexa.share.permission_check_context.content.user_content_type_identifiers` container parameter. | ||||||
| It accepts an array of content type identifiers and the default value is `['editor']`. | ||||||
|
|
||||||
| You can now restart you application and start [working with the Collaborative editing feature]([[= user_doc =]]/content_management/collaborative_editing/work_with_collaborative_editing/). | ||||||
| To add the real-time editing capabilities, continue with the instruction below. | ||||||
|
|
||||||
| ## Configure real-time editing | ||||||
|
|
||||||
| You must have an arrangment with [[= product_name_base =]] before configuring the real-time editing. | ||||||
| If you haven't already, you must also accept the Terms of Service in the [Service portal](https://support.ibexa.co/). | ||||||
|
|
||||||
| Only then you can create a new Collaborative editing environment. | ||||||
| To do it, log in to the service portal, go to your **Service Portal** and select **Create environment** (this requires the **Portal administrator** access level). | ||||||
|
|
||||||
| Once the environment is created, you can proceed with the configuration in [[= product_name =]]. | ||||||
|
|
||||||
| Use the generated values to set the `environment_id`, `environment_secret`, and `web_socket_url` for your [repositories](repository_configuration.md) as in the example below: | ||||||
|
|
||||||
| ``` yaml | ||||||
| ibexa: | ||||||
| repositories: | ||||||
| default: | ||||||
| fieldtype_richtext_rte: | ||||||
| environment_id: '%env(CKEDITOR_ENVIRONMENT_ID)%' | ||||||
| environment_secret: '%env(CKEDITOR_ENVIRONMENT_SECRET)%' | ||||||
| web_socket_url: '%env(CKEDITOR_WEB_SOCKET_URL)%' | ||||||
| ``` | ||||||
|
|
||||||
| Then, enable real-time editing for specific [SiteAccesses](siteaccess.md). | ||||||
|
Check failure on line 201 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
| The following example enables it for the back office: | ||||||
|
|
||||||
| ``` yaml | ||||||
| ibexa: | ||||||
| system: | ||||||
| admin_group: | ||||||
| fieldtype_richtext_rte: | ||||||
| enabled: true | ||||||
| ``` | ||||||
|
|
||||||
| Finish the configuration by running: | ||||||
|
|
||||||
| ``` bash | ||||||
| composer run post-install-cmd | ||||||
| ``` | ||||||
|
|
||||||
| ## Accepting new Terms of Service | ||||||
|
|
||||||
| Real-Time Collaboration service is only available after accepting its Terms and Conditions. | ||||||
| Any new version of this document released by [[= product_name_base =]] must be accepted before the assigned deadline. | ||||||
|
|
||||||
| The **Portal administrator** for your [Service portal](https://support.ibexa.co) can accept it in Service portal's service details. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd keep it here, as there can be multiple service portals |
||||||
|
|
||||||
| If not done in time, the Real-Time Collaboration service will be disabled until the latest Terms and Conditions are accepted. | ||||||
|
Check warning on line 225 in docs/content_management/collaborative_editing/install_collaborative_editing.md
|
||||||
Uh oh!
There was an error while loading. Please reload this page.