AnqiCMS (AnqiCMS) Template Tag Manual
The PHP official policy is to provide full support for each branch starting from the stable version, and then handle only critical security issues as needed for the next two years. According to the deadline on the current page, 8.2 to December 31, 2026, 8.3 to the same year in 2027, 8.4 to 2028, 8.5 to 2029. The site scheduling should separate these two stages and leave at least one complete regression cycle, and do not wait until the patch stops before starting.
The order should be to define the site structure first, then translate the content, and finally configure the switch entry. The structure selection determines all subsequent work: whether it is a multilingual site or a site segmented by market, it directly affects the domain, content, and maintenance boundaries. The full-page HTML translation can cover the text, but template copy, glossary, and product attributes need to be reviewed separately; the switch entry should be released only after the language version can be verified to avoid visitors switching to a half-translated page.
The PHP official policy is to actively support each branch for two years, and then add two more years for fixing only critical security issues. For example, the active support for 8.2 ends on December 31, 2024, and the security support extends to December 31, 2026; the security support for 8.3, 8.4, and 8.5 respectively ends at the end of 2027, 2028, and 2029. The bottom line for a site completing a major version upgrade is the end date of the security support for that branch, and it is a safe practice to start scheduling after entering the security-only stage.
The static alias modifies the address resolution entry, and if the rules are mistakenly damaged, the first problem to appear is with links containing query parameters, pagination, tag pages, and Chinese paths. There are similar repair records in the update logs of third-party open-source systems. This article provides the five types of links that must be tested before going online, the configuration order and rollback method of custom static alias rules, as well as which link to fix first when enabled simultaneously with the 301 redirect.
Before using the bulk replacement function to change content on the entire site, it is recommended to back up three types of objects: document data (including static files), template files, and navigation and watermark configurations. Keywords and links in the text can be covered by the recycle bin and piece-by-piece rollback, but once configuration items such as navigation, watermark, and template are overwritten, there is no ready-made recovery entry. Take a snapshot before replacement and confirm the correct scope after replacement with front-end inspection.
Migrating in a fixed sequence ensures not losing indexing: First export the content list and make a complete backup, then use ZIP compression packages or Excel spreadsheets to batch import content. When importing, check for duplicate titles to avoid repeated搬运, and finally, set up 301 redirect mappings for old addresses and observe for two weeks. This article provides the key operational points and verification methods for each step, covering the backup scope of data and static files and the usage standards of the import interface.
The old site articles are moved in bulk, the choice between ZIP compressed package import and Excel table import depends on whether there are attachments and field structure: The migration of image static files and graphics goes through the compressed package, while batch creation of articles goes through field mapping. AnQiCMS also provides the import/archive import interface, which supports querying whether the title already exists, and can be checked before repeated import.
When scheduling holidays in advance, the scheduled release solves the timing point, and the draft status to be released solves the review progress. AnQiCMS divides documents into four states: formal, draft, scheduled release, and recycling bin. The draft link with preview parameters can be reviewed before release, and deletion is moved to the recycling bin instead of physical deletion. There is a fallback path if scheduling fails.
Check the access chain on the day of the host switch: whether the resolution points to the new host, whether the certificate is complete and available at the new address, whether the pseudo-static rules and 301 redirect are effective, and whether the form and interface can be written. Before the switch, lower the validity period of the resolution record and make a complete backup containing static files. After the switch, keep the old account for more than a week and observe the log and traffic distribution. The record of the email sending identity should also be checked separately.
Cache is divided into three layers according to resource type: static products such as images and attachments are placed in the outer layer, and page content such as list pages and detail pages are placed in the middle layer and can be set with a shorter expiration period, and back-end and interface caching is not performed. The purpose of layering is to make the source only happen in the truly real-time part, and the page loading speed is improved accordingly, while the immediate visibility of back-end changes will not be blocked by caching.
