HTML Blocks: setup and help

Upload and install the HTML Blocks ZIP in Modules > Module Manager. Open HTML Blocks > Blocks. Configure opens the module configuration page; the Blocks page contains the content editor.

Create a block with Internal Name, enter Content for your languages and save. Add a display location to make it appear. A saved block without an active placement has no storefront position.

Create blocks with the built-in editor; no additional model file is required.

For a footer message, you can enter:

<div class="footer-trust">
  <strong>Secure payment</strong>
  <span>Pay using a payment method enabled in this shop.</span>
</div>

Set Internal Name to Footer - Payment message, leave Title empty, use CSS Class footer-trust-block, and keep Cookie Consent Required at None (always show) for an ordinary text message.

In multistore, review the intended shop context and fill Title and Content for each required language. These two fields have language- and shop-specific records. CSS Class, the block Active switch and placement definitions are shared rather than separate translated fields. Native-hook rendering selects content for the current shop and language and skips a block with no usable content. Check each shop and language after changing a shared block or placement.

In the block's placement panel, choose Display Location and Layout, then add the location. The visual preview opens the shop with hook markers so you can inspect supported locations. A theme must actually render the hook for its placement to appear.

You can reuse a block at several locations. The same block cannot be added twice to the same native hook through the placement action.

Available locations include:

For a homepage banner, use displayHomeIntro, Layout full-width and a suitable class such as homepage-seasonal-banner. For a footer message, use displayFooter and contained.

Create the translated block, set Title to the tab label and add displayProductTabContent as its display location. The module supplies the tab label and content through product-tab hooks. Your theme must support those hooks.

For a Delivery tab, use Internal Name Product - Delivery Tab and Title Delivery. Add your delivery content and save. Check the tab on an actual product page, including its label and content in each language.

The product-tab label and content both follow the block’s consent requirement.

Use HTML Blocks > Templates when the theme has no suitable native hook at the required position. Back up the theme first. The PHP process needs write access to the affected theme files or child-theme override path, plus the PrestaShop cache.

1. Scan the active theme. Supported page types include Product, Category, Listing, Manufacturer, Supplier, All Brands and CMS.
2. Review the proposed file, position and hook call for the page type.
3. Accept or inject the selected position. The manager can modify the template or create an extends override where supported.
4. Assign an existing block to the page profile and choose its layout and insertion position.
5. Keep the profile active and save its settings.
6. Open a matching storefront page and check the location.

The manager inserts marked Smarty content using the module hook:

{* MPR_HTMLBLOCK_INJECT *}
{hook h='displayMprHtmlBlock'}
{* /MPR_HTMLBLOCK_INJECT *}

Generated calls may include page-specific parameters. Preserve those when using the manager's suggested call. A developer can also place {hook h='displayMprHtmlBlock'} manually, but must account for the intended page context and placements.

The profile's active state defaults to on. After a theme update, use Check Status. If markers are missing or the position is stale, scan again before reinjecting. Remove All removes tracked injections. Use the manager to remove a tracked position instead of deleting marker fragments by hand.

Selector-based placement support also exists. Use native hooks or Template Manager for the ordinary setup workflow; selector placement depends on stable theme markup.

For optional embeds or scripts, choose a category in Cookie Consent Required. The module emits inert encoded content and inserts it in the browser only after the MPR Cookies Revolution client exposes a grant for that category. With no decision, refusal or no usable MPRCR client, the gated content stays absent. Withdrawing consent removes inserted content.

This lifecycle applies to native hooks, template placements, selector placements and product tabs. A block's own category can also be insufficient for an embedded script that needs another category.

Keep essential page text ungated. Consent-dependent content can appear after page load, move the layout and remain absent for crawlers without consent. Use None (always show) for content that should always be present.

Do not manually forge consent cookies. The category names used by the integration are functional, analytics and marketing; the consent module owns the visitor's decision.

Open HTML Blocks > Settings > Configuration > Theme styles. The shared style editor starts with detected theme values and lets you override them. Use Refresh shop styles after a theme change. Use Clear custom styles to return to detected values.

The module maps background, secondary background, border, text, muted text, radius, shadow and transition to its mpr-card style tokens. In the shared editor, these correspond to Primary surface, Secondary, border Normal, text Body and Muted, Default radius, Default shadow and Transition. Existing shop overrides can change the values.

For local CSS, use your CSS Class and the stable content wrapper:

.mpr-html-block-content img { max-width: 100%; height: auto; }
.mpr-html-block-content table { width: 100%; border-collapse: collapse; }
.footer-trust-block .mpr-html-block-content {
  display: flex;
  gap: 1rem;
  align-items: center;
}
.homepage-seasonal-banner.mpr-html-block-full-width {
  padding-top: 2rem;
  padding-bottom: 2rem;
}

There are no start/end scheduling fields, customer-group targeting fields or per-product/category ID targeting fields in the standard block editor. Use the block, placement and page-profile active switches as applicable.

Check the block in each language, at each assigned location and at phone and desktop widths. Disable one placement to confirm that the other locations remain available. Disable the whole block to hide all its placements.

For a gated block, test undecided, granted, refused and withdrawn states in a browser with the consent module running. Check both the product-tab label and panel if you use tabs.

If nothing appears, check block Active, placement Active, language content, profile Active and whether the theme renders the hook. For gated content, check the consent decision and browser JavaScript errors. For an injected position, run Check Status and inspect the proposed template file.

If a title remains visible after choosing No title, clear the Title field. The current template renders a nonempty title with an empty tag in a div.

Use Settings > Integrity to check and repair required module tables. If styles or content remain stale, clear the relevant PrestaShop and page/CDN caches and check theme template overrides.

Back up blocks, placements and the theme before uninstalling. The module removes tracked template injections before removing menu entries and calling schema cleanup. If it cannot remove injections, uninstall reports failure so you can fix file access and retry. Module-owned tables are removed by schema cleanup; export any content you want to keep first.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.