Aller au contenu

Why is the Bricks template detected but the listing still shows the default Listdom layout?

Ce contenu n’est pas encore disponible dans votre langue.

You created a Bricks template for Listdom single listing pages, and Bricks appears to detect the template, but the frontend listing page still shows the default WordPress/Listdom layout instead of your Bricks design.

This can happen with the Listdom Bricks Addon Bricks when the listing page is still set to render with WordPress instead of Bricks.

You may see one or more of these signs:

  • The template looks correct inside the Bricks editor.
  • The frontend listing page still shows the default Listdom single listing layout.
  • The WordPress admin bar shows Rendered with WordPress.
  • The admin bar still shows Edit with Bricks, but the Bricks template is not applied on the frontend.
  • The listing content appears as a default Listdom pre-made layout instead of your Bricks template.

Bricks includes an admin-bar render mode that lets an enabled post type render with either WordPress or Bricks. If a listing page is set to Rendered with WordPress, the frontend output uses the WordPress rendering engine even if Bricks can detect the assigned template.

In this state, the related Bricks template may exist and open correctly in the editor, but the final listing page does not render through Bricks.

  1. Log in as an administrator.
  2. Open the affected listing page on the frontend.
  3. Look at the WordPress admin bar.
  4. If you see Rendered with WordPress, open that menu.
  5. Click Render with Bricks.
  6. Refresh the listing page.
  7. Clear any site, server, CDN, or optimization plugin cache if needed.

After switching the page back to Bricks rendering, the assigned Bricks template should apply to the listing page.

If the issue continues, also check the following:

  1. Go to Bricks → Templates.
  2. Confirm the template is published.
  3. Confirm the template condition targets the Listing post type.
  4. Make sure the Listing post type is enabled in Bricks settings.
  5. Confirm there is no other Bricks template with a higher-priority condition.
  6. If you use Polylang or another multilingual plugin, make sure the Bricks template exists for the correct language.
  7. Clear all cache and test again in a private/incognito browser.