Document Content History retention and version creation scope - #3386
Open
derrickmehaffy wants to merge 4 commits into
Open
Document Content History retention and version creation scope#3386derrickmehaffy wants to merge 4 commits into
derrickmehaffy wants to merge 4 commits into
Conversation
Content History had no retention section at all, so there was no way to answer how long versions are kept, and nothing stated that versions are only created for edits made through the Content Manager. Writes from the REST and GraphQL APIs, the Document Service API, lifecycle hooks, cron jobs, and the import and transfer commands create no version. Co-Authored-By: Claude <noreply@anthropic.com>
The parameter controls how long Content History versions are kept but was never documented, unlike the analogous auditLogs.retentionDays. Adds it to the full configuration examples and states that it can only shorten the retention period defined by the license. Co-Authored-By: Claude <noreply@anthropic.com>
The note duplicates the one under the Audit logs section and refers to auditLogs.retentionDays, which is unrelated to transfer tokens. Co-Authored-By: Claude <noreply@anthropic.com>
The TL;DR feeds llms.txt, so surfacing the 90-day maximum and the Content Manager scope there makes both facts reachable without reading the page. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
pr: updated content
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR documents two Content History behaviors that the documentation did not cover at all, both of which support currently has nothing to cite when customers ask.
strapi importandstrapi transfercommandshistory.retentionDaysparameter on the admin panel configuration page, mirroring the existingauditLogs.retentionDaysentry, and adds it to the full configuration examplesBehavior was verified against
packages/core/content-manager/server/src/historyin strapi/strapi.