Common misconfigurations in the contact information settings of AnQi CMS: Make your contact information clear and visible

In website operation, clearly and effectively displaying contact information is a key link in building user trust, promoting communication, and business transformation.AnQiCMS provides a convenient backend setting and template tags, allowing you to easily manage and call these key information.However, even such convenient features are often affected by some seemingly minor configuration mistakes, leading to contact information not being displayed normally on the front page, causing confusion to operators.

As an experienced website operations expert, I am well aware that these 'small problems' may hide user experience gaps. Today, let's delve into the 'Contact Information Settings' in Anqi CMS andcontactCommon configuration mistakes between template tag calls and clear solutions provided.

Backend settings: Management of the 'origin' of contact information.

First, let's review the contact information settings of the Anqi CMS backend. You canHome page > Backend settings > Contact information settingsFind these configuration items. Here are default fields such as "contact person", "contact phone number", "contact address", "contact email", "WeChat ID", and "WeChat QR code" for your convenience in entering the basic contact information of your company.

The strength of AnQi CMS lies in its flexibility, you can also add contact methods that meet your specific needs through "custom settings parameters", such as "WhatsApp account" or "Facebook homepage link" etc. There are several details to be aware of when setting these custom parameters:

  1. Parameter name:This is the unique identifier for template use. Anqi CMS suggests setting the parameter name to English, and the system will automatically convert it to camel case (i.e., the first letter of each word is capitalized, and there are no spaces in between) for easy use in templates.For example, if you have customized a parameter name such as 'WhatsApp' in the background, then you can directly use it in the templateWhatsApp.
  2. Parameter value:This is the actual contact information content, such as phone numbers, email addresses, and so on.
  3. Note:Only used for backend management, to facilitate your understanding of the parameter usage, and will not be displayed on the front end.

Understanding these backend settings is the first step in correctly calling the contact information. Because the template tags need to know exactly where to get the data.

contactTag calling: A bridge connecting the backend and frontend

In the Anqi CMS template file,contactTags are used to display the contact information you set in the background on the website. Their basic usage method is:{% contact 变量名称 with name="字段名称" %}Of course, if it is only a simple direct output of a field value,变量名称it can also be omitted.

here,nameThe attribute is the core, it tellscontactwhich contact information you want to get from the background settings.

Common configuration mistakes and solutions

Now, let's analyze several that are commonly encountered when usingcontactconfiguration mistakes when labeling, and provide solutions one by one.

Misconception one: Neglecting the precision and case sensitivity of the 'parameter name'

This is the most common and easiest mistake to make. Many operators set up contact information in the background, and when calling the front-end template, they often encounter issues because of thenameThe inaccurate understanding of attribute values leads to the inability to display information.

  • Problem manifestation:

    • Built-in fields such as 'Contacts' are called in the front-endname="username"but expected to be displayed.
    • The custom field is set to "My WhatsApp" in the backend and called in the frontendname="myWhatsApp"orname="WhatsApp", but found nothing.
    • The system prompts "The specified field was not found".

  • Deep reasons:Safe CMS template tagsnameThe value of the attribute requires high precision and strict distinction of case.

    1. Built-in fields:The built-in contact information fields all have fixed camel case English naming.