In AnQiCMS (AnQiCMS) template development,prevArchiveTags are a very practical tool that can help us easily implement the navigation function of "Previous document" on the article detail page, thereby optimizing the user's browsing experience.As a website operations expert, I am well aware of the importance of smooth page transitions and convenient content discovery for user retention and SEO.However, concerningprevArchiveDoes the tag support parameters to filter or specify the previous document, which is often a question many users have when exploring the functions of AnQiCMS.
Today, let's delve into it deeplyprevArchiveThe functionality and performance of the tag in practical applications.
prevArchiveThe core function and design philosophy of the tag.
First, let us make it clearprevArchiveThe core function of the label: It is designed to retrieve the "previous" document data of the current document, usually used at the bottom of the article detail page to guide users to continue browsing related content.This contextual navigation is an effective means to improve user experience and reduce the bounce rate in website operation.
From the design philosophy of AnQiCMS,prevArchiveThe tag reflects its 'simple and efficient' characteristics. It focuses on providing the most direct and general previous document link, aiming to reduce the complex configuration for template developers.Therefore, according to the official document of AnQiCMS,prevArchiveThe tag is designed to bedoes not support any parametersTo filter or specify a previous document of a particular type.
This means that you cannot directly go throughprevArchiveTags to limit that the previous document must belong to a specific category (categoryId），a certain module（moduleId），or with a specific recommended attribute（flag）。The system will automatically determine which document is the "previous" document based on its built-in logic (usually based on document ID or publication time in the current context).
prevArchiveWhat information can the label provide?
ThoughprevArchiveThe tag itself does not accept parameters, but it successfully retrieves the "previous" document objectprev(This is usually named in the template, such as{% prevArchive prev %}) can provide rich document information, this information is enough to build a complete previous document navigation. The available fields include:
- Id: The unique identifier ID of the document.
- Title: The title of the document.
- Link: The access link of the document.
- Keywords: The keywords of the document.
- Description: Brief description of the document.
- CategoryId: The ID of the category to which the document belongs.
- Views: Document views.
- Logo: Document cover first image address.
- Thumb: Document cover thumbnail address.
- CommentCount: The number of comments of the document.
- Created Time: The document creation time (timestamp format).
- Updated Time: The document update time (timestamp format).
By these fields, we can easily display the title, link, and even thumbnail of the previous document in the template, thus providing users with intuitive navigation.
Considerations and examples in practical application
While usingprevArchiveWhen labeling, the most important practice is to add a judgment to ensure that the current document indeed exists a "previous" document. If the current document is already the first in the series or sorting, thenprevThe object will be empty, directly accessing its properties will cause an error.
This is a typicalprevArchiveLabel usage example:
{% prevArchive prev %}
<div class="archive-navigation">
{% if prev %}
<a href="{{ prev.Link }}" title="{{ prev.Title }}">
{% if prev.Thumb %}
<img src="{{ prev.Thumb }}" alt="上一篇：{{ prev.Title }}" class="archive-thumb" />
{% endif %}
<span>上一篇：{{ prev.Title }}</span>
</a>
{% else %}
<span class="no-prev-archive">没有更多上一篇了</span>
{% endif %}
</div>
{% endprevArchive %}
This example shows how to use safelyprevArchivethe tag, first judgeprevwhether the object exists, and then display its title, link, and thumbnail.
When a more complex 'previous article' logic is needed
SinceprevArchiveIf no parameters are accepted, how should we handle more complex logic such as "only get the previous document in the same category", "only get the previous document with specific tags", or "sort the previous documents by views"?
In this case, we need to bypassprevArchivethe limitations, adopting a more flexiblearchiveListtags combined with template logic to achieve.archiveListtags support various parameters to filter and sort documents, such ascategoryId/tagId/orderWait. We can use it firstarchiveListGet a list of documents that meet the conditions, then manually find the document that comes before the current document in the list as the "previous one".
This usually involves more advanced template programming techniques, which may require more processing on the backend controller or frontend JavaScript. For AnQiCMS, a system that pursues simplicity, prevArchiveThe single-functionality of the tag is to cover the vast majority of general 'previous article' navigation needs, while leaving more complex logic to developers to implement through combinations of other tags and logic, maintaining the lightweight nature of the core function.
In summary,prevArchiveThe tag does not support parameters, but its concise design and rich information output make it a powerful and easy-to-use tool for building basic document navigation in AnQiCMS.Understanding its design intent and capability boundaries will help us use AnQiCMS more efficiently to create an excellent website experience.
Frequently Asked Questions (FAQ)
Q1: IfprevArchiveHow does it decide which document is the 'previous' one if the tag does not support parameters?A1:prevArchiveThe tag is determined by the default document sorting logic of the AnQiCMS system to determine the 'previous' document.This is usually based on the publication time of the document (in descending order) or the document ID (in ascending order), and find the document that follows in the module or category to which the current document belongs.It will automatically return the previous document based on the position of the current document in the overall list.
Q2: Can I only display the 'Previous' document that belongs to a specific category or has a specific tag?A2:prevArchiveThe tag itself cannot directly implement the "Previous" function with filtering conditions. If your need is to get the previous document under a specific category or tag, you need to use it in combination witharchiveListLabel. First usearchiveListBased oncategoryIdortagIdFilter out the list of relevant documents based on parameters, then use custom template logic to find the document that comes before the current document in the filtered list. This will be more efficient than usingprevArchiveMake it more complex.
Q3: If the current document is already the first in the series,prevArchivewhat will the tags return?A3: If the current document is the first in the sorted list, there is no previous document,prevArchiveThe variable defined by the tag (for exampleprevwill be empty (nil).When using it in the template, be sure to pass through{% if prev %}Such conditional judgment to avoid errors and display custom prompt information when there is no previous one, for example, "There are no more previous ones."