So Outside Technology Security CMS
AnQiCMS
Online Demonstration

The test version announcement is only suitable for test environments, and how to set up a pre-release site.

📅 October 26, 2026 👁️ 0

The announcement is written for self-test and is only suitable for test environments, the original text is intended for testing and development only, and the actual meaning of this sentence is that verification must be completed in another environment, not on the official site.WordPress was released on October 20, 2026, as 7.2 Beta 1. The announcement clearly states that it is intended for testing and development only, and should not be installed or run on production or critical business sites. Please use a testing environment or local site.This kind of verification is carried out by a pre-release site that is the same version, configuration, and data form as the official site.

Is the pre-release environment and test version the same thing

No. The test version refers to the software version being in the gray release stage, and the pre-release refers to a fixed-purpose environment: it runs the formal version or the version to be launched, and the data is a copy of the formal site, which is not accessible to the outside world.

The relationship is: the trial version can only be run in the pre-release or local environment, while the pre-release environment serves not only the trial version - high-risk actions such as template revision, batch import, and structural migration also require it. It is treated as a temporary machine for trying out new versions once, and is usually discarded after two uses.

How to replicate data and configuration

The first step is a data copy. Export a complete set of data from the official library, including documents, categories, tags, and static files. AnQiCMS supports the backup and recovery of data and static files. The backup generated is the starting point for duplication. After importing the copy into the pre-release environment, the volume of content on both sides is consistent, and the verification conclusions have migration value.

The second step is to configure duplication. Three areas are most likely to be missed: pseudo-static rules and site structure, authorization and captcha switch, and third-party service configuration items. These may run under default values, but may not perform the same under customized configurations of the formal site.

The third step is to align the deployment form. The official site uses the Docker image anqicms/anqicms for deployment, and pre-release also follows the same path; the official site is deployed in the Baota or aaPanel environment using the panel, and pre-release is also deployed using the panel. Details such as listening to port 8001 by default, the reverse proxy layer needs to be replicated in the form of the official site, otherwise the upgrade verification is of 'environment differences' rather than the version itself.

How to isolate the content status

In the pre-release environment, new content will also be generated. When verifying, it is necessary to distinguish between 'This is test data' and 'This is the content to be launched'. AnQiCMS has document states such as formal documents, drafts, to be published, and recycling station, and it is the most convenient to use it for isolation:

Complete all destructive verification writing with drafts, the draft link with the preview parameter can be previewed without being caught by the outside; confirm the manuscripts to be launched to the pending release, which is equivalent to marking a clear batch mark for the synchronization action of the formal station; discard data generated during the test process is directly deleted into the recycle bin, and decide whether to restore or clear it after the verification is completed to avoid test manuscripts mixing into the formal index.

Acceptance list

The first pre-release verification should at least cover the following actions, record whether each item passes or fails:

Back-end login and permission, publishing and classification tag, image upload and display, front-end rendering after template modification, batch import of paragraph positioning, data integrity after upgrade or version switching, once a real backup and restore drill. The last item is often omitted, but it is precisely what determines whether the pre-release environment is really available on the day when a problem occurs.

The online experience station plays another role in this process: it is suitable for verifying functions and interactions before deciding to adopt a system, without duplicating data. Using the experience station as a pre-release will result in an environment with different data volume and configuration, and the verification conclusion has no persuasiveness for the official site.

Copy level comparison table

Copy item Must be consistent Can be simplified
Data copy and static files Is No
Version and configuration items Is No
Deployment method and reverse proxy Is No
Content status isolation Is No
Access traffic No Simplified to zero
external domain name No use internal address instead

Common questions

should the pre-release environment be kept running all the time?it is recommended to keep it running long-term but reduce the configuration specifications. It is only accessed during verification, can be started and stopped according to the verification window, and avoids continuous maintenance.

can the data from the official site be changed directly?no. Do the verification directly on the official repository, any misoperation is immediately visible to the public, and the premise of isolation is that the data is a copy.

how to synchronize to the official site after the verification is passed?replay the steps confirmed in the pre-release, rather than covering the entire environment. The difference is only in the data and configuration sources, and the steps themselves have already been verified.

Related articles

Before going live, use the online experience site to inspect the functionality, which can help identify real problems in advance.

Before going live, use the online trial site to verify the function, which can help to discover three types of real problems in advance: the background action path is inconsistent with expectations, the function has an entry but lacks key configuration, and it is impossible to judge the scope of impact of batch operations. The trial site verifies the function and interaction, while deployment, data migration, and backup recovery require a separate test instance to be run independently, with two people responsible for a section of verification each.

2026-10-26

Who should do the full site replacement and 301 redirect first when multiple site groups are revised together

When multiple site groups are redesigned together, first determine the new site's pseudo-static rules and set up the 301 redirect table, and then perform the full site replacement. The two actions modify different objects: redirection manages URL ownership, and replacement manages keywords and link text in the main text. The wrong order will allow the same round of crawling to see both old and new addresses at the same time, causing collection to fluctuate back and forth, and batch verification by site is the key to closing the mouth.

2026-10-26

How to avoid simultaneous online launch of scheduled releases for multi-site groups

When multiple site groups share a set of scheduled release schedules, the impact of simultaneous online launch falls on the crawling and indexing queues: at the same time, a large number of page changes occur, the marginal benefits of crawling decrease, and the inclusion pace actually slows down. Peak-shaving is divided into three steps: group by site to open up time windows, give up the whole points, and reserve time slots for revision and backup; the order of priority is arranged according to the impact of inclusion, not according to the size of the site, and the status of pending release is used to carry the schedule instead of as a draft.

2026-10-26

Import in bulk using both zip packages and tables. When images and fields do not match, check which side first

When importing in bulk, check the table side first and then the image side: if fields do not match, it is mostly because the column names and custom fields are not aligned, and if images are missing, it is mostly because the file paths in the zip package do not match the names referenced in the table. AnQiCMS supports ZIP package and Excel imports, the import interface can be queried by title to check if it already exists, and it should be used to judge before repeating the execution

2026-10-26

How to arrange the order of sensitive word filtering and manual review before the collected content goes live

The order before the content goes live is: first draft, then sensitive word filtering and keyword replacement, followed by manual review, and finally the formal document is changed. The rule layer is responsible for determinable issues, the manual layer is responsible for facts and scope, and the recycling station catches accidental deletions. Reversing the order will allow low-quality content to enter the visible range of search with a complete index.

2026-10-26

What are the recovery methods available in the background if an article is deleted or modified

First, determine whether it was a deletion error or a modification error. In AnQiCMS, the deletion action is to move the formal document to the recycle bin, not a physical deletion, and it can be restored from the recycle bin; for modification errors, check if there are draft and historical versions of the pending release status. If there are no rollback versions available, there is only the last line of defense, which is the data backup, and the backup range should include static files, and it should be verified regularly whether it can really be restored.

2026-10-25

Before importing tens of thousands of documents in bulk, you need to confirm which few things

Before importing tens of thousands of documents in bulk, you need to confirm the field mapping, duplicate check, batch rhythm, and rollback path. This article takes the AnQiCMS ZIP and Excel batch import, and document content import interface as an example, explaining the inspection methods before import, and how to recover after import errors using the recycle bin and backup.

2026-10-25

How do the fields and tags correspond between the Chinese and English stations?

When the Chinese and English stations share a set of content models, the field correspondence should follow the principle of 'define structure first, then language': use a custom content model to define bilingual common fields, maintain Chinese-English matching words with a keyword library, the whole page HTML translation is responsible for the final draft, and multi-site management is responsible for switching and isolating. This article provides common errors in field mapping and the implementation methods of label correspondence.

2026-10-25