A classification/list enhancement plug-in for Z-BlogPHP.

core functions

In the category page and the GetList list called on the home page, modules and templates, the main category article of the specified category will be compared with the category that is called as "additional classification"articles are merged (mixed in reverse order according to release time), and the aggregated display of parent categories including child categories and configurable caching strategies are supported.

Suitable for any content aggregation website that requires "multiple presentations in one article": such aswebsite navigation, Tutorials/Learning,resource download, special topic/information portal and other sites that want the main category + additional categories to be exposed at the same time.

story editor

additional functions

At the same time, the plug-in also solves the problem of too many categories on the website, which makes it very difficult to find pain points when selecting categories, and supports keywords.Search Select Category(fuzzy search), and the first most matching search result will be automatically selected. In this way, even if the website has hundreds or thousands of categories, you don't have to worry about finding difficulties!
You need to have more than 10 website categories to use this function!

Plug-in advantages

1. Safety

The plug-in will not modify or reuse the system's built-in log_CateID field. After deactivation, the original classification display logic will remain normal, and there is no risk of data pollution.

2. Data storage

The additional classification IDs are stored independently in the newly added field log_ExtraCateIDs (formatted as a comma-separated set of IDs) and do not interfere with the main classification field.

3. Performance optimization

Built-in caching policy (configurable validity period) reduces database pressure caused by multi-category matching and statistics, and ensures response speed under scenarios with increased internal capacity.

4. Theme compatibility

It is implemented in the "hook + data rearrangement" method, with zero changes to themes and core files; after uninstallation, the system restores the original behavior, no residual dependence, and there is no need to manually restore the template.