So Outside Technology Security CMS
AnQiCMS
Online Demonstration

Can deleted articles be retrieved, and how are drafts, pending publication, and recycling stations divided?

📅 2026-11-01 👁️ 0

Can deleted articles be recovered? AnQiCMS documents are divided into four categories: formal documents, drafts, pending publication, and recycling station. Deleting a formal document is moving it to the recycling station rather than a physical deletion. As long as the content is still in the recycling station, it can be restored. What truly determines whether it can be recovered is the status it was in when deleted, as well as whether a rollback backup was left.

What are the four categories?

Official documents are visible to the public and can be searched; drafts are incomplete or content that is not intended to be publicly shared, appearing only in the background; pending release is content that has been written but not yet effective, waiting to go live at a scheduled time; the trash can holds deleted documents, acting as a buffer between recovery and complete cleanup. These four states separate 'completion' and 'going live', and break 'deletion' into two steps to avoid one action causing two consequences at the same time.

Why is deletion first sent to the trash can?

The risk of physical deletion lies in its irreversibility, while deletion within content management is often a misjudgment: choosing the wrong batch range during column reconstruction, confusion with documents with the same name, or just wanting to temporarily take down. Moving to the recycling bin gives these operations a chance to change their minds, and thorough cleaning should be done from the recycling bin. The recycling bin does not bear the responsibility of archiving, and long-term retention should follow the draft or an independent archive classification.

Who can open the draft link?

The draft itself does not appear in the public list, but AnQiCMS supports draft links with a preview tag for previewing, which is convenient for colleagues or clients to see the layout and content before going live. This means that the preview link is accessible, but the content is in draft status. Two points to note: do not directly promote the preview link externally, and do not place unconfirmed quotes, commitments, or event information in the draft - once the link is opened, it cannot be guaranteed that it will only spread within the expected range.

The relationship between scheduled publishing and timed publishing.

The factor that needs to be released in coordination is the timing factor——timed release. Setting the content to go live at a specific time point has the advantage of decoupling writing and publishing, allowing for advance preparation and scheduled implementation, and also avoiding the manual operation period. It is important to note that the timed release should be coordinated with other actions on the site: After a batch import, set the release rhythm uniformly, which is easier to verify than setting the time individually; if a withdrawal is needed temporarily, it should be changed back to draft before it takes effect, and after it takes effect, it can only go through the path of deletion into the recycling bin.

The safe order for batch cleaning

The batch operation is most likely to go wrong, and a fixed sequence can keep the risk under control. The first step is to confirm the scope, filter by category or tag and then select all, do not use the whole table selection; the second step is to back up first, AnQiCMS backup covers data and includes static files, so that you can roll back the whole thing if you delete in bulk by mistake; the third step is to execute in small batches, check the recycle bin content and front-end performance between batches; the fourth step is to clean up the recycle bin, and only perform a complete deletion when you are really not needed anymore. If you just need to temporarily take down, going through draft or scheduling is more appropriate, and you do not need to use deletion.

Common questions

Will the content in the recycle bin be kept forever?Cannot assume permanent preservation. The recycle bin is a buffer position, important content should be recovered and archived separately, long-term reliance on the recycle bin for preservation is equivalent to no backup.

Will the documents recovered return to their original position and state?The actual status on the site should be taken as the standard. After recovery, the columns, URLs, and publishing status should be checked, especially for documents with scheduled releases, to avoid immediate public effectiveness after recovery.

If you just want the article to be temporarily not public, which status should be used?Change it back to draft instead of deleting. Deleting will cause the content to enter the recycle bin, and switching the status off temporarily is faster, and it will not occupy the recovery process.

Related articles

How to import articles from the old station table once, if the fields do not match

The order of handling the mismatch of fields when importing the exported table of the old station to the new system is: first select the channel and then discuss mapping, the three columns of fixed title, alias, and category must be mapped, then determine the default value strategy for custom fields, and finally use title search to check if it already exists to avoid repeated imports and sample check the import results

2026-11-01

For articles sent at scheduled times, should the page cache be refreshed again?

Set the article for timed publishing to be released on time, and check whether the main content page, list and home page cache, and sitemap are in sync. Static generation and state transition are two steps, the cache of the list page is often behind the detail page, and the new address also needs to enter the sitemap and cooperate with link push, so that the timed publishing can truly be seen.

2026-11-01

After the translation of the multilingual site is completed, should the page address of each language be generated separately?

After the full-page translation of a multilingual site is completed, each language should have a stable and accessible independent page address, and a sitemap should be generated separately by language for easy verification. Language tags solve the problem of displaying the correct version of search and AI retrieval, but do not improve ranking. This article gives the verification sequence and common mistakes after going online.

2026-11-01

How to see the default switch of a new site placed in a back-end system?

When multiple sites share the same backend, the default switch of a new site only checks three things: which batch of sites the default value of the site status affects, whether the access entry and content structure are properly matched, and the difference between closing and deleting. This article provides the check sequence for a new site and explains the fallback role of the recycle bin and backup in the multi-site scenario.

2026-11-01

How to plan the column structure and classification for a single backend to manage multiple sites without conflict

When managing multiple sites with a single backend, the place where column structure and classification are most likely to interfere with each other is when reusable definitions and isolated data are mixed together. This article explains by separating the shared layer and the isolation layer: the definition of the content model can be reused across multiple sites, the classification tree, column aliases, and visibility range should be planned independently for each site, batch operations at the whole-site level are disabled by default and explicitly enabled per site, and a landing sequence and a corresponding table are provided.

2026-11-01

When starting a site with a container image, should the default port and background address be changed together?

When starting a station using a container image, whether to change the default port and backend address at the same time depends on where the traffic comes from: After the site is behind the reverse proxy, the container listening on port 8001 only needs to match in the mapping, the default port does not need to be changed; what needs to be received is the exposed surface of the backend address. Before going online, enable the built-in protections such as JWT authentication, sensitive word filtering, captcha, and rate limiting first, and then verify it once from the external network.

2026-11-01

Several thousand articles need to be moved, should it be imported using a compressed package or a table?

When moving thousands of articles, the basis for choosing between compressed package import and table import is not the quantity but the material form: batch import using ZIP compression packages for text with attachments and rich text, and batch import using Excel tables for neatly organized fields. First align the content model and custom fields, and then use the import interface for title duplication check to control duplicates, and only the failed batches can be safely rerun.

2026-11-01

When the sitemap exceeds the limit, it can only be split into files, and before splitting, you need to clear which type of address.

The site map exceeds the single file limit and must be split into multiple files using an index file for aggregation, but before splitting, it is necessary to clean up three types of addresses: pages with error status codes, redirect addresses, and pages with屏蔽 marks that are written into the map. The cleaning order is wrong, and the each file after splitting is still wasting crawling quota, the collection efficiency will not improve.

2026-11-01