Feature preview
Email reminders should be configured in three layers: the system settings layer places the sending channels and switches, the business module layer places the recipient rules for messages and orders, and the collaboration layer places content publication and pending reminders. AnQiCMS's email reminders, message lists, and order management are all in different layers, and the rules should be placed in the module that triggers them to avoid all notifications being crammed into the same email.
Leaving a message, order and release reminders all go through email, where should the email reminder rules be configured? According to the triggering party, they should be layered: the sending channel and the master switch are configured in the system settings layer, the recipient rules for messages and orders are configured in their respective business module layers, and the reminders for content release are configured in the editing collaboration layer. Place the rules in the module that generates the event, so that notifications will not all flood into the same email, and it will also be clear later who triggered a particular email.
| Notification type | Triggering event | Recipient | Where should the rules be configured? |
|---|---|---|---|
| Operating status class | System events, subscriptions, and backup results | Site administrator | System settings layer |
| Business action class | New message, order status change | Customer service or operations manager | Business module layer |
| Editing and collaboration | Scheduled publishing at points, pending content | Editor and reviewer | Collaboration process layer |
The standard for stratification is 'who needs to know immediately.' If the running status class has a problem, it affects the entire site, the scope of recipients is small; business action class every day, recipients should be divided by position rather than by person; editing and collaboration are bound to the release rhythm, and it should be sent only when the content truly enters the process.
AnQiCMS's email reminder capability is responsible for two things at the system level: whether the email sending channel is available and whether the notification function is enabled. This layer does not decide who's message is sent to whom, it only ensures that the email can be sent out. It is a common mismatch to write the recipient rule at this layer, resulting in all events being sent to the administrator, and important operational alerts being overwhelmed by message emails.
The message notification is hung on the message module. The background message list processes new messages centrally, and with the help of email reminders, the notification is achieved, and the recipient should be the person responsible for the reply, not the whole-site administrator. Starting from v3.6.5, the background also added the ability to subscribe to emails, and subscription emails and message reminders belong to different paths, and the recipient list and unsubscribe processing should not be mixed.
The order notification is hung on the order module. AnQiCMS supports WeChat official account connection, order management, financial management and distribution management, the status changes of order events are many, the rules need to be triggered according to the status: pending payment, completed, and refund to decide whether to send and to whom. After turning on the notifications of the whole order flow, after dozens of repeated emails a day, the recipient will start to ignore them.
When using the API to batch write content or read data, it is easy to ignore notifications that are also triggered. AnQiCMS provides an interface for importing document content, where you can see the high-frequency capabilities covered by the document list and details, categories and tags, upload pictures, comments and replies, friendship links, system settings and contact information. If the batch import is directly converted into formal documents, batch reminders for publication will be generated. A safe practice is to first import drafts in bulk and leave the reminders to be confirmed manually before sending them.
Can the same event send to multiple recipients?Can, but the recipient list should be maintained at the business module level to avoid hardcoding at the system level; only one place needs to be changed when changing positions.
What should I do if there are too many notifications and I want to turn off some of them?Turn off from the trigger point instead of from the channel: turn off low-value status change reminders first, keep running alarms and messages requiring replies, and do not directly stop the messaging channel.
How to coordinate the release reminder with the scheduled release?The scheduled release arranges content to go online at a specific time, reminders should be sent at the 'already online' or 'online failed' nodes, rather than at the scheduled plan.
Preview
The process of entering information, adding images, tagging, writing title descriptions, and scheduling publications can be automated. Fact verification, risk statements, and external communication must be confirmed by personnel. This article analyzes the AI writing, automatic title image matching, AI automatic tagging and TDK, batch import, and scheduled publishing capabilities of AnQiCMS in five stages, and provides the manual checkpoint settings for each stage.
Preview
Can the entire site migration be blocked from the backend: The ones that can be blocked are the mass crawling of machines, but not the manual rewriting. AnQiCMS uses anti-crawling interference codes to change the text obtained by the crawling end, uses sensitive word filtering and content review to control the quality of entry, uses robots configuration to define the crawling boundary, and then relies on the time factor left by scheduled publishing as the first release evidence.
Preview
Parameter binding handles the injection risk of input being executed as a statement, sensitive word filtering handles text content violations, and the two have different points of action, judgment criteria, and consequences. AnQiCMS entrusts the query to the GORM and Iris framework layer convergence, and sets up sensitive word filtering, keyword replacement, and review process on the content side, and the two lines cannot be replaced for each other.
