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
Copy file name to clipboardExpand all lines: docusaurus/docs/dev-docs/configurations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Some specific features require additional configuration:
43
43
|[Cron jobs](/dev-docs/configurations/cron)| <ul><li>In the `/config/server` file to enable the feature</li><li>In a dedicated, optional `cron-tasks` file that can be used to declare the jobs</li></ul> | Required to setup CRON jobs for the server. |
44
44
|[Environment variables](/dev-docs/configurations/environment)| In dedicated files and folders for the environment (e.g., `config/env/production/server`) | Optionally used to define different environments and their variables. |
45
45
|[Single Sign-On (SSO)](/dev-docs/configurations/sso) <EnterpriseBadge /> | In the `config/admin` file | Required to use the Entreprise-only SSO feature if enabled on your project. |
46
-
|[Feature flags](/dev-docs/configurations/features)| In the `config/features` file | Optional for a typical, stable Strapi application.<br/>Only required to enable [future flags](/dev-docs/configurations/features).|
46
+
<!--| [Feature flags](/dev-docs/configurations/features) | In the `config/features` file | Optional for a typical, stable Strapi application.<br/>Only required to enable [future flags](/dev-docs/configurations/features).|-->
Copy file name to clipboardExpand all lines: docusaurus/docs/user-docs/content-manager/adding-content-to-releases.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Instructions to include content in a release
4
4
displayed_sidebar: userDocsSidebar
5
5
---
6
6
7
-
# Including content in a release <EnterpriseBadge /> <CloudTeamBadge /> <FutureBadge /> <BetaBadge />
7
+
# Including content in a release <EnterpriseBadge /> <CloudTeamBadge />
8
8
9
9
Using the [Releases](/user-docs/releases/introduction) feature, you can group several entries to publish them altogether. Adding entries to a release is done from the Content Manager. You can also remove an entry from a release while updating the entry.
10
10
@@ -35,17 +35,17 @@ To add entries to a release:
35
35
}}
36
36
/>
37
37
38
-
## Adding a single entry to a release
38
+
## Adding an entry to a release
39
39
40
-
An entry can be added to a [release](/user-docs/releases/introduction) while editing it from the edit view of the Content Manager.
40
+
An entry can be added to a [release](/user-docs/releases/introduction) while editing it from the edit view of the Content Manager. Only collection type entries can be added to a release, not single type entries.
41
41
42
42
To add an entry to a release:
43
43
44
44
1. In the Releases box in the right sidebar, click the **+ Add to release** button.
45
45
2. Select which release to add this entry to.
46
46
3. Decide whether the entry will be published or unpublished when the release itself is published, then click **Continue**.
47
47
48
-
## Removing a single entry from a release
48
+
## Removing an entry from a release
49
49
50
50
An entry can be removed from a [release](/user-docs/releases/introduction) while editing it from the edit view of the Content Manager.
# Creating a release <EnterpriseBadge /> <CloudTeamBadge />
7
7
8
8
The [Releases](/user-docs/releases/introduction) page allows creating new releases that will be used to organize entries.
9
9
@@ -26,7 +26,7 @@ To create a new release:
26
26
27
27
Adding entries to a release must be done from the Content Manager. You can add a single entry to a release while creating or editing the entry [in the edit view](/user-docs/content-manager/adding-content-to-releases).
28
28
29
-
<!-- TODO: for later, when multiple addition is implemented -->
29
+
<!-- TODO: for later, when multiple addition is implemented, probably in 4.20-->
30
30
<!--
31
31
Adding entries to a release must be done from the Content Manager:
Releases enables content managers to organize entries into containers that can perform publish and unpublish actions simultaneously. A release can contain entries from different content types and can mix locales.
9
9
10
-
11
-
Releases is currently only available as an experimental feature. To enable it, set the appropriate future flag. See <ahref="/dev-docs/configurations/features">future flags</a> documentation for instructions on how to enable a future flag.
# Managing a release <EnterpriseBadge /> <CloudTeamBadge />
8
8
9
9
Adding entries to a [release](/user-docs/releases/introduction) allow viewing them altogether on a single page.
10
10
@@ -36,28 +36,30 @@ You can rename a release. To do so, while on a release page:
36
36
3. In the modal, change the name of the release in the _Name_ field.
37
37
4. Click **Continue** to save the change.
38
38
39
-
## Choose how entries are grouped
40
-
41
-
:::callout 🚧 Beta feature
42
-
Use the following command to install the latest version of this feature:
43
-
`npx create-strapi-app@beta`
44
-
:::
39
+
## Choosing how entries are grouped
45
40
46
41
A release page can display entries either grouped by locale, content-type, or action (publish or unpublish). To change how entries are grouped, click the **Group by …** dropdown and select an option from the list.
47
42
48
-
## Publish or unpublish entries
43
+
## Publishing or unpublishing entries
49
44
50
45
A release includes multiple entries. You can set the state of each entry with the **Publish** and **Unpublish** action buttons. When the release itself is “published” then the desired actions will be simultaneously performed on each entry.
51
46
52
-
<!-- TODO: re-add when implemented -->
53
-
<!-- ## Remove entries from a release
47
+
## Removing entries from a release
54
48
55
-
Entries can be removed from a release. To do so, click the three dots **…** at the end of the line of an entry and select the **Remove from release** button.-->
49
+
Entries can be removed from a release. To do so, click the at the end of the line of an entry and select the **Remove from release** button.
56
50
57
51
## Publishing a release
58
52
59
53
Publishing a release means that all the actions (publish or unpublish) defined for each entry included in the release will be performed simultaneously. To publish a release, click the **Publish** button in the top right corner of the admin panel.
60
54
55
+
The _Status_ column displays the status of each entry:
56
+
57
+
- Already published: the entry is already published and publishing the release will not affect this entry
58
+
- Ready to publish: the entry is ready to be published with the release
59
+
- "[field name] is required", "[field name] is too short" or "[field name] is too long": the entry cannot be published because of the issue stated in the red warning message.
60
+
61
+
If some of your entries have a  status, click the  and the **Edit the entry** button to fix the issues until all entries have the  status. Note that you will have to click on the **Refresh** button to update the release page as you fix the various entries issues.
62
+
61
63
:::caution
62
64
Once a release is published, the release itself cannot be updated. You can not re-release that specific release with the same group of entries with some modifications; you must create another release.
0 commit comments