In the template development of Anqi CMS,userGroupDetailTags are important tools for obtaining detailed information about specific user groups.When we need to display user group names, descriptions, levels, or their settings on the page, this tag is used.idandlevelThese two parameters are used to specify the user group to be queried, so what are the differences between them, and how should they be selected for use?

UnderstandinguserGroupDetailtags

Firstly, let's briefly review.userGroupDetailThe function of the tag.Its main function is to retrieve all relevant data of a user group based on the given identifier (which can be a user group ID or user group level), such as the name of the user group (Title), introduction (Description), purchase price (Price), and so on.This allows template developers to flexibly display exclusive content or features for different user groups.

When calling this tag, you need to go throughnameThe parameter specifies the specific fields of the user group to be retrievedidandlevelThe parameter is used to accurately locate which user group.

idParameter: A precise unique identifier

idThe parameter usually refers to the unique digital identifier of the user group within the system.It can be thought of as the 'ID card number' for each user group, which is a fixed number that usually does not change and precisely points to a user group record in the database.

When to useidParameters:

When you are in the following scenarios, you usually choose to useidParameters:

  • Precisely refer to a known user group:If you know the unique ID of a specific user group and want to get its information directly,idThis is the most direct and accurate way.For example, you may have seen the ID of a user group in the background user group management interface and wish to hardcode it in the frontend template (although hardcoding is not recommended, it may be used for quick testing or referencing built-in fixed user groups sometimes).
  • Associated with other data:When your other data (such as user data) stores the user group ID of the user and you want to query the details of the user group through this ID,idThe parameter is an ideal choice.
  • Strongly associated backend logic:If certain business logic (such as permission judgment, payment function) strictly depends on the unique ID of the user group, it will be more robust to display relevant information through the ID in the template.

Example usage:If you want to get the name of the user group with ID 1:

<div>用户组ID为1的名称：{% userGroupDetail with name="Title" id="1" %}</div>

levelParameter: flexible level identifier

levelThe parameter represents the level of the user group, which is usually a string or number with semantic meaning, used to describe the hierarchy or category of the user group.For example, you may have set levels such as "VIP_Level_1levelMay be more appropriate in some cases thanidfor better readability.

When to uselevelParameters:

In the following situations,levelThe parameter would be a better choice:

  • Query by level or role:If your user group is divided by different membership levels, permissions, and you want to display content dynamically based on these level names,levelParameters will be very convenient. For example, you want to display the exclusive description for all "Gold Member" user groups.
  • Template logic is clearer:Use directly in the templatelevel="VIP_Gold"may be more thanid="7"Easier to understand and maintain, especially when you are not familiar with the specific ID correspondence.
  • Configurable hierarchy system:If your user group level system is configurable in the background (for example, level names or corresponding permissions may be adjusted), but you want to refer to it by logical names in the template,levelThe parameters can provide this kind of flexibility.

Example usage:Assuming your system has aVIP_Level_1user group level, you want to get its name:

<div>VIP等级为VIP_Level_1的名称：{% userGroupDetail with name="Title" level="VIP_Level_1" %}</div>

idWithlevelSelection and considerations

UnderstoodidandlevelAfter understanding the respective uses, the most important difference lies in:These two parameters are mutually exclusive, you cannot use them at the same time.When you calluserGroupDetailWhen labeling, you must and can only chooseidorlevelone of them to specify the user group.

How to choose:

  • Prioritize business semantics:If your template logic is more focused on the 'level' or 'role' concepts of user groups, and these level names are relatively stable, then usinglevelIt makes template code more readable and maintainable.
  • Prioritize stability:If you need to refer to a user group that has fixed and infrequently changing attributes at the system level (for example, a special system administrator group), thenidIt is usually a more stable choice because it is less likely to change due to business level adjustments.
  • Consider the data source:What information (ID or Level string) you can easily access in the current template context will also affect your choice.

In short,idProvided an accurate, unchanging unique identifier, suitable for scenarios where strict, direct referencing of user groups is required; andlevelThen provided more semantically meaningful and hierarchical identification, suitable for scenarios where content is dynamically displayed based on the roles or levels of user groups. Choose reasonably based on your specific needs and the focus of the template logic.idorlevel，will help to build clearer and more efficient security CMS templates.

Common Questions (FAQ)

  1. Question: Can I use parametersidandlevelto get user group information? Answer:No.userGroupDetailTagsidandlevelThe parameters are mutually exclusive, you can only select one to specify the user group in a single tag call.

  2. Question: If I go throughlevelThe parameter referred to a user group, but later the background modified the level name of this user group. Will the template be affected? Answer:The content will be affected. If the user group level name in the background changes, and your template still uses the old one.levelIf the tag does not find a matching user group due to the value query, the information will not be displayed normally.idThe parameter is usually a unique and unchanging identifier for a user group within the system, therefore it isidused when referring to it. Even if the name of the level changes, as long as the ID remains the same, the tag will still work normally.

  3. 问：Where can I view the user groups in the AnQi CMS backend?idandlevelinformation? Answer:You can find this information in the "User Group Management" or related "Member Settings" module on the Anqi CMS backend.通常，用户组列表会显示其ID和名称，而用户组的详细编辑页面则会包含其等级（Level）的配置项。