In AnQiCMS flexible and versatile content management, we often need to display content on the article detail page, and the main content of the article is usually displayed througharchiveDetailLabel combinationContentTo retrieve the field. But sometimes, due to various operational needs, we may need to make some subtle adjustments to the content of these articles, such as unify the brand name, correct specific vocabulary, or temporarily hide certain information. In this case, directly modifying the original text in the database may be inconvenient, or we may need a more flexible display strategy. 幸运的是，AnQiCMS provides powerful template filter functions, where replaceThe filter is a powerful assistant for dealing with such problems.

Get to knowarchiveDetailwith the tag andContentfield

First, let's briefly reviewarchiveDetailTags and what they provide.ContentField. In the AnQiCMS template system,archiveDetailThe tag is used to obtain the detailed data of a single article (or document, AnQiCMS refers to it as "document")When you visit the detail page of any article, it will automatically identify the article ID of the current page and provide all relevant information about the article.

Among them,ContentThe field contains the main content of the article, which is usually written in HTML structure through a rich text editor or Markdown editor. In the template, we usually display the article content like this: 

{# 假设我们已经在一个文档详情页，并想获取当前文档的内容 #}
{% archiveDetail articleContent with name="Content" %}
{{ articleContent|safe }}

Pay special attention here|safefilters. Due toContentThe field may contain HTML tags, the AnQiCMS template engine defaults to escaping the output to prevent potential security issues (such as XSS attacks). Plus|safeA filter, it informs the template engine that this content is safe and can be directly parsed as HTML, ensuring that the layout and style of the article are displayed normally.

Why do you need to replace in the templateContentcontent?

You might be puzzled, since the content can be edited directly in the background, why do you still need to replace it at the template level? There may be many reasons:

  1. Brand name or term unification:During the operation of the website, brand names or industry terms may be slightly adjusted, such as from "AnQiCMS" to "AnQiCMS".If the number of articles is large, it takes time and effort to modify the background content one by one, and it is easy to miss.Use in templatereplaceFilter, can achieve global (for articles rendered by the current template) unified replacement, improve efficiency.
  2. Temporary sensitive word processing:Some content may not be suitable for public display at the moment, or may need to be expressed in another form. ThroughreplaceFilter, it can temporarily replace or hide these words without modifying the original text.
  3. Dynamic information embedding: Combine other template variables to replace certain fixed text in the article with dynamic links, contact information, etc., to increase interactivity or marketing effectiveness.
  4. A/B testing:Display different versions of certain keywords in the article title or body to test user feedback without frequently modifying the database.

These scenarios emphasize the flexibility and convenience of content adjustment during front-end rendering.

replaceHow to use the filter

AnQiCMS template engine supports a variety of filters,replaceIt is one of them. It can help us find specific old words in a string and replace them with new words. The basic syntax is very intuitive:

{{ 变量名|replace:"旧词,新词" }}

The 'old word' and 'new word' should be separated by an English comma,It should be noted that:

  • If the 'old word' is empty,replaceThe filter matches at the beginning of the string and after each UTF-8 character sequence, which usually results in inserting 'new words' between each character.
  • If the "new word" is empty, it is equivalent to deleting all matched "old words".

InarchiveDetailinContentUsereplace

Now, we willarchiveDetailtags,ContentandreplaceCombine the filters. Suppose we want to replace all occurrences of "AnQiCMS" in the article content with "AnQiCMS", we can do this:

{% archiveDetail articleContent with name="Content" %}
{{ articleContent|replace:"安企CMS,AnQiCMS"|safe }}

If your article content needs to be replaced in multiple places, you can chain multiplereplacefilters together, which will execute in order from left to right:

{# 假设还要将“内容管理系统”替换为“CMS系统” #}
{% archiveDetail articleContent with name="Content" %}
{{ articleContent|replace:"安企CMS,AnQiCMS"|replace:"内容管理系统,CMS系统"|safe }}

If you need to remove a specific word from the article, for example, remove all occurrences of the phrase "old version":

{% archiveDetail articleContent with name="Content" %}
{{ articleContent|replace:"旧版本,"|safe }} {# 注意“新词”留空 #}

Emphasize again|safeusage: due toContentThe field usually contains HTML structure, and any replacement operation should be followed by|safeA filter to ensure the browser can correctly parse the final HTML content, avoiding tags being escaped into plain text.

Some practical tips

  1. Case sensitive: replaceFilters are typically case-sensitive. For example, 'AnQiCMS' and 'anqicms' are considered different words.If you need case-insensitive replacement, it may be necessary to combine other methods (such as converting all text to uppercase or lowercase before replacing, but AnQiCMS'sreplaceThe filter does not directly support regular expressions or case-insensitive options).
  2. Efficiency and maintenance:Even though the replacement of content in the template is very flexible, if the replacement logic is too complex or numerous, it may slightly affect the rendering efficiency of the template and increase the maintenance difficulty of the template itself.For large-scale, frequent, or complex replacement needs, it is recommended to prioritize the "Full Site Content Replacement" feature provided by the AnQiCMS backend, which is performed at the data processing level, with higher efficiency.
  3. Does not affect the original text:Perform in templatereplaceThe operation will only affect the final display effect of the current page content and will not modify the original content stored in the database. This provides great flexibility and security for content display.

ByarchiveDetailTag to get article content and use it cleverlyreplaceA filter, AnQiCMS operators can fine-tune the display of article content without touching the database, to adapt to changing content strategies and user needs.This undoubtedly brings more convenience and possibilities to daily content management work.

Frequently Asked Questions (FAQ)

Q1:replaceWill the filter modify my article content in the background editing interface?

A1:No.replaceThe filter is a data processing operation performed by the AnQiCMS template engine during page rendering.It only affects the final content displayed in the user's browser and does not make any modifications to the original article content stored in the database.The backend editing interface still displays the original article content.

Q2: If I want to replace a word uniformly throughout the entire website, for example, replacing all articles from "old company name" to "new company name", replaceIs the filter a **choice?

A2:For unified replacement across the entire site, the AnQiCMS backend provides a special "Unified Content Replacement" function (usually under "Function Management" or "Content Management").This feature can directly modify the article content in the database in batches, which is more efficient and also meets this kind of requirement.template ofreplaceThe filter is more suitable for local or temporary content adjustments for specific templates and scenarios.

Q3:replaceDoes the filter support using regular expressions for more complex replacements?

A3:Built-in of AnQiCMS templatereplaceThe filter is mainly used for simple string to string replacement and does not support regular expressions.If you need to replace content based on complex patterns and want to implement it at the template level, you may need to look for whether AnQiCMS community provides more advanced custom filters, or consider regular expression processing at the backend code level (for example, before data is passed to the template).