AnQiCMS (AnQiCMS) is favored by a wide range of content operators for its flexible content model and efficient operational capabilities. Today, we will delve into a common concern: when we adjust the content model parameters in the background, the front-end page usingarchiveFiltersWill the filtering conditions of the tag display automatically update?

As an experienced website operation expert, I can clearly tell you that the answer is yes:When the parameters of the content model in AnQi CMS backend are adjusted,archiveFiltersthe filtering conditions displayed by the tags will be automatically updated.

The core concept and dynamism of AnQi CMS

To understand this, it is first necessary to review the core design philosophy of Anqi CMS.In the 'AnQiCMS Project Advantages' document, we see that 'Flexible Content Model' is listed as one of the core features.This means that the system has fully considered the variability of content structure from the beginning of its design, allowing users to customize content types and their fields according to business requirements.This flexibility is not only reflected in the input and display of content, but also in the dynamic interaction capabilities of the front-end page, such as filtering and sorting.

The strength of AnQi CMS lies in the fact that it does not statically write backend configurations into the front-end template, but instead reads and interprets the latest content model definitions in real time when the page is requested to be rendered. This dynamic rendering mechanism is exactly whatarchiveFiltersThe key that allows the label to automatically update its filtering conditions.

archiveFiltersHow tags work

archiveFiltersTags (seetag-archiveFilters.mdDocuments) specifically used to generate filtering conditions based on custom fields of the content model on document list pages or category pages.Its design goal is to help users perform combination filtering based on the various "parameters" (i.e., custom fields) of the content.

It is explicitly stated in the document:

"Filter parameters are only available in list typestype="page"[en]The setting takes effect at the moment, and the filtering parameters only need to be placed in the query parameters of the URL.In the additional automatic configuration of the document, configurable fields are set up, which can be used to filter the document by appending these fields to the query parameters of the URL.

This tells us,archiveFiltersTags are not generated out of thin air as filtering conditions, but rather depend on the custom fields that are explicitly defined as 'filterable' in the backend content model. When the page loads, this tag will query the specified content model (viamoduleIdRetrieve all the custom fields and their preset values (such as radio, checkbox, dropdown options) that can be used to filter under this model.Then, it constructs the front-end filtering interface based on this real-time acquired information.

The implementation mechanism of dynamic response model parameter adjustment.

Imagine a scenario: You are running a real estate website and have created a content model named 'Real Estate'.Initially, you may have only defined fields such as 'House Type' (e.g., residential, commercial) and 'Area'.archiveFiltersTags will generate corresponding filter options based on these fields.

If one day you decide to add a field named "Type" and in the "Content Model Usage Help" on the backend,help-content-module.mdIn it, preset values such as "one bedroom one living room

  1. The AnQi CMS template engine encounters when rendering a page,archiveFiltersLabel.
  2. archiveFiltersthe tag will query the latest definition of the "Real Estate" content model from the system.
  3. The system returns the updated model definition, which includes the newly added "house type" field and all its preset options.
  4. archiveFiltersTags are dynamically generated on the page based on these real-time data, creating new 'apartment type' filtering options and displaying options such as '1 bedroom 1 living room', '2 bedrooms 2 living rooms', and so on.

The entire process is automatically completed, no manual modification of template code is required, and no additional configuration refresh is needed.This seamless transition experience greatly enhances the efficiency and flexibility of content operation.

Summary

Anqi CMS'sarchiveFilters

Common Questions (FAQ)

1. I modified the content model parameters in the background, but the front-end pagearchiveFiltersdid not update the displayed filter conditions immediately, why is that?

This situation is usually caused by browser caching.Although the backend of Anqi CMS will update the data in real time, your browser may be loading an old cached page.Try clearing the browser cache or force refresh the page (usually Ctrl+F5 on Windows, Cmd+Shift+R on Mac) to see the updated filter conditions.If the issue still exists, it may be due to certain caching mechanisms on the server side. In this case, you can try clicking the 'Update Cache' feature in the Anqi CMS backend to clear the system cache.

2.archiveFiltersWill the tag display the filter conditions for all custom fields in the content model?

Not necessarily.archiveFiltersTags will display those custom fields that are configured as 'filterable' in the content model.Generally, when the backend defines custom fields, there is an option to control whether the field appears in the frontend filter.archiveFiltersAs seen.

3. If my custom field has many different values (such as text input boxes),archiveFiltershow would you handle these filtering conditions?

archiveFiltersTags are mainly used for field types with clear, limited options (such as radio buttons, checkboxes, dropdown selections) to generate visual filtering conditions. For custom fields of free text input type,archiveFiltersusually does not generate dropdown or checkbox-style filters, but expects to pass through the URL'squeryParameters are passed directly with keywords for filtering.This means that filtering for such fields may require you to manually construct the URL or through the search box.The document mentions that 'the filtering parameters only need to be placed on the query parameters of the URL' also implies this kind of processing method.