AnqiCMS (AnqiCMS) Template Tag Manual
When the back-end login port is repeatedly attempted, changing the access address only reduces the passive exposure area, but the real way to reduce the probability of success is another three layers: identity and token management, automated submission control, and high-risk operation domain switch for automated tools. This article provides executable changes for these three layers and explains the order of handling after attempts, including verification of credential rotation and backup recoverability.
The website loads slowly, do not guess first whether it is a program or a server. Use three steps to divide the responsibility: first, measure the first byte time of static pages and dynamic pages separately, then find the inflection point under concurrency, and finally look at the actual resource usage rather than the configuration list. After completing the three steps, you can clearly determine whether the responsibility lies in program processing, entry configuration, or insufficient resources, and then decide whether to upgrade the program or add resources.
The rule matching of crawling protocol has a clear sequence: the spider finds its rule group in a case-insensitive way, and falls into the wildcard group if it can't find it; the path rules take effect according to the most specific one, which is unrelated to the writing order. In the face of multiple AI crawlers with different purposes, whether to write separate rules depends on whether you want to distinguish training crawling from question and answer reference crawling. This article provides the method of judgment and configuration sequence.
The lastmod in the sitemap should write the last modified time of the page, not the generation time of the sitemap file itself, this is clearly written in the protocol document. This article explains the semantics of the field, what consequences will bring the date to be brushed to today when the entire site is re-generated, and what types of pages are worth writing, as well as the two pitfalls to pay attention to in format and time zone
When releasing three versions in twenty days, the follow-up window for security patches should not be queued according to the version number, but should be categorized according to the type of fixes in the announcement: those with security fixes should be handled on the same day, pure defect repairs should be scheduled for this week, and only new features can be observed. This article provides the criteria for the three-time limits, the checklist before upgrading, as well as the rollback points and where to keep backups.
Navigation, single-page, and friend links are the three most easily overlooked maintenance items on the site. If the column adjustment does not rearrange the navigation, it will leave isolated pages; addresses and contact information written in single pages will become outdated if not changed for a year; when the detection of link expiration and lack of standards for external text is lacking, problems are usually discovered by the cooperative party. This article provides the operational actions, anchor text and interface capabilities for each of the three, as well as the method of determining the maintenance cycle according to events.
This is a batch rewrite of the entire site, with risks concentrated on the scope and the irreversible aspects. The safe order is to first make a recoverable backup, then narrow down the scope to a small amount of content for testing, confirm the hit results before executing officially, after execution, establish 301 redirects one by one according to the old address, and finally check that the recycle bin and drafts are not involved. Omissions are often found in navigation and single-page applications, and incorrect changes often come from too broad matching words. This article provides checkpoints for each step.
When there are more spam comments, three types of protection each manage a section: captcha judgment to determine whether the submission action is initiated by a machine, sensitive word filtering and content review to determine whether the submitted text can be exposed externally, and frequency control to limit the number of submissions from the same source within a short period of time. No section can fill the gap of another, and the wrong order may result in the situation where many switches are turned on but spam still comes in. This article divides it into before submission, during submission, and after submission, and explains the easy-to-miss XSS risk where the content to be reviewed is still rendered in the background.
The key to not stacking anchor text within the site is to first build a keyword library, then determine the scope of distribution: a keyword should point to only one target page, the number of times the same word appears on a single page is controlled, and the rules are effective according to the column rather than the entire site. The essence of automatic anchor text is to replace in bulk, and rule conflicts will overlap, so the configuration order is more important than the switch itself.
The correct sequence after being hacked is to cut off the still effective entry first, then clean the files, then complete the entry vulnerability repair and review in the same round, and finally change the credentials. Simply cleaning the files without moving the entry will definitely recur: the number of files is hundreds or even thousands, and manual inspection and identification are not complete, and leaving an unrepaired entry means that the next round of writing is just a matter of time.
