Skip to content
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

FR: Archived entry status #4223

Kashkin opened this issue May 7, 2019 · 1 comment


None yet
2 participants
Copy link

commented May 7, 2019

We've found that many enterprise or government clients request archive functionality.

For most clients, we are able to push them towards disabling entries, but for large websites with hundreds or thousands of entries, the interface becomes cluttered and their requirements are not being met.

An Archived entry status would address this. Archived entries wouldn't show up on the Entries index page unless specifically filtered to (much like how "Trashed" currently works). An Archive button could be added next to the Delete button on an Entry page. Archived pages are otherwise identical to Disabled pages, and can still be accessed via Share links or Live Preview. It would also allow for template queries to access Archived pages and display them in specific contexts.

#877 would also address this, but I feel that a specific, core entry type for archiving content would be of use to many developers without overcomplicating the interface or code-base.


This comment has been minimized.

Copy link

commented May 8, 2019

One option is you could disable hard deletion entirely, so soft-deleting elements effectively archives them in perpetuity.

You can do that by setting the softDeleteDuration config setting to 0 from config/general.php.

'softDeleteDuration' => 0,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.