Custom Category H1: setup and help

Follow the steps in Quick start.

Open Custom Category H1 > Category Headings. Click Add category heading. In Category, select one or more categories. The selector supports specific categories, condition groups and exclusions. A new form starts with nothing selected. Root categories cannot be selected because they do not render ordinary storefront category pages.

Enter Custom H1 in each required language. The stored field is limited to 255 characters. Set Active to Yes and save. One override can assign the same text or pattern to multiple categories. A category cannot have two assignments in the same shop context. If the editor reports an existing assignment, edit that override instead.

You can also open Catalog > Categories and use Custom H1 heading on the category edit form. When a category belongs to a shared override, editing it here detaches only that category. The other categories retain their shared assignment. Empty values can still resolve through the enabled language, shop or parent fallbacks.

Open Configuration. Settings are organized into four tabs. Defaults below are installed values; an existing shop can have different saved values.

General

Back office

Front office

Safety

Save after changing settings. The module stores headings in mprcustomcategoryh1_override, mprcustomcategoryh1_override_lang and mprcustomcategoryh1_override_category, using your database prefix. It does not update native category names in the database.

Examples:

Buy {category_name} Online
{category_name} - {nb_products} Products
{category_name} {page_label}
{category_name} for {shop_name}
{category_name} - {lang}

With category name Shower Trays, {category_name} {page_label} gives Shower Trays - Page 3 on page 3. On the first page, whitespace normalization removes the trailing space. Include the space before {page_label} yourself.

The module replaces category headings and product-listing labels on the server. It does not replace headings through JavaScript. Your theme must display the category heading or listing label supplied by the module.

The original category name remains saved. After enabling replacement, review menus, breadcrumbs and other theme locations: custom templates that reuse the category heading can also show the replacement.

For a custom theme, a developer can use the supplied variables directly:

{if isset($category.mpr_custom_h1) && $category.mpr_custom_h1}
  <{$category.mpr_custom_h1_tag|default:'h1'}>{$category.mpr_custom_h1|escape:'html':'UTF-8'}</{$category.mpr_custom_h1_tag|default:'h1'}>
{else}
  <h1>{$category.name|escape:'html':'UTF-8'}</h1>
{/if}

This module does not edit meta titles, meta descriptions, URLs, canonical tags or category descriptions.

If the normal name remains, check Enable, the override's Active state, category selection, current shop, translation and fallback settings. For a stock theme, keep Replace category name on category page enabled. Check other modules that also change category output.

If the heading changes after filtering, check Apply to product-listing label and the theme's AJAX templates. If a heading repeats across child categories, review Fallback to parent category override. If a translation unexpectedly uses another language, review Fallback to default language.

Use Integrity for module setup checks. Configuration, License, Support and Update are separate module admin pages.

Set Enable to No to stop replacement, or set an override's Active switch to No for a narrower change. You can delete an assignment from Category Headings. Fallback rules can still supply another heading.

Use Uninstall in Module Manager to remove the module. Its uninstall removes its schema tables, configuration and admin menu. Save a database copy of your heading assignments first if you need to retain them. Native category names remain available after removal.