The core function module provided by AnQi CMS, helping you quickly build an enterprise website
Functional Icon
Since version 3.6.5, the Anqi CMS background file search supports double-layer wildcard, which expands the search range while also increasing the area of misfire. This article provides the process of defining the scope before batch modification: first list the hit list according to wildcard, then narrow down the matching range to the actual directory to be modified, perform single test modification and batch execution through the site-wide replacement tool, and explain what records to keep before and after the modification for rollback
Functional Icon
Human verification shifts from selecting images to risk-based clearance, Cloudflare Turnstile provides hosted, non-interactive, and invisible three forms, the checkbox only appears when the risk is high. The token handed over to the backend does not mean security, the server still needs to verify the source, grade the form scenario, and provide a return that can be processed in case of verification failure.
Functional Icon
When downloading attachments, the Chinese file name is garbled, mostly because only filename or only filename* was written in the response header. The specification document states that both should be written together: parameters with an asterisk should be encoded in UTF-8 percentage encoding and have higher priority, while those without an asterisk should retain ASCII form for compatibility with old clients. This article also explains why the directory separator needs to be replaced.
Functional Icon
The interface documentation is aimed at the caller, explaining how to make requests and what public capabilities are available; the site description file is aimed at the large language model, helping the model understand and index the website content. Both have different readers and different functions, one manages calls and the other manages solutions, and both should be crawlable. The site description file is automatically generated by the system, working with the site map to divide labor: the site map manages discovery, and the description file manages solutions.
Functional Icon
When managing multi-brand, multi-theme websites with a single system, the site boundary determines the domain and backend entry, the language level determines the translation scope, and the content model determines whether fields are shared. The domain and main site language are independent of the site, the template and content model can be chosen between shared and independent, and navigation and single pages are maintained separately by the site.
Functional Icon
Automatically tag, keyword library, and anchor text management play different roles at different levels: tags belong to this article, the keyword library belongs to the entire site's word table, and anchor text is responsible for linking words to internal pages. This article explains the order of effectiveness in the publishing process, when they will affect each other, and suggestions for division of labor in multi-site scenarios.
Functional Icon
Comment spam filtering blocks automated submission, which occurs at the moment of the form; comment review blocks the content itself, which acts before the content is stored and published. The two defenses manage different things, and only one configuration will result in obvious mismatched performance. This article explains the steps at which they act and the order of configuration.
Functional Icon
友情链接 is the address of the opposite site placed in the external exchange position, and anchor text is the internal link automatically generated by the keywords within the site. The two have different objects, maintenance entry, and fallback methods. This article explains where they are configured, who will read these links, and what order to operate when rewriting the text in bulk.
Functional Icon
Long-tail keywords scattered across multiple articles, the closing path is to first enter the keyword library, then determine the corresponding relationship between words and targets by anchor text rules, then replace and supplement historical articles with the full site, and finally ensure the stability of the address with pseudo-static addresses and links. This article explains what each configuration manages and the order of operation.
Functional Icon
The system supports custom static URL, so the address format can be redesigned according to the category and document type. Changes will involve four aspects: automatic generation of sitemap, 301 redirect configuration, anchor text placement and internal link reference. This article gives the order of first determining the form, then setting the jump, and finally submitting, and explains how to preserve the positions on the old form and the checklist for item-by-item verification after the change.
Functional Icon
After the content site opens distribution, reconciliation is done in three steps: the records in order management are the factual source, first check the interval and status; distribution management is derived from the attribution view of the order; financial management summarizes it into the account口径. The user group decides which part of the background roles can see, confirm the backup before exporting to cover data and static files, and recover copies for checking in case of anomalies.
Functional Icon
WeChat Official Account integration and in-site user system are two chains: the former manages message and fan reach, and the latter uses user groups and VIP groups to determine access permissions. Whether to connect depends on whether the site has membership content and order scenarios; when connected, only identity mapping is done, and authentication is still completed in-site, the interface layer goes through built-in JWT authentication, and permission determination does not look at external identity identifiers.
