*

aga2442

  • **
  • 11 posts
Hello,

On the item detail page, two different sources are both printing Open Graph / Twitter meta tags into the same <head>, with conflicting values for the same properties:

1) OSClass core: oc-includes/osclass/structured-data.php (~lines 134-150)
   - og:title, og:site_name, og:description, og:image, og:type="product"
   - also emits twitter:card/title/description/image and a JSON-LD Product schema

2) Epsilon theme: item.php (~lines 105-110)
   - og:title, og:site_name, og:description, og:image, og:type="article"
   - no twitter: tags, no JSON-LD

Both blocks render on the same page, so og:title, og:description, og:site_name and og:type each appear twice with different content, and og:type conflicts outright ("product" vs "article").

This is not specific to our install — it reproduces identically on your own official demo:
https://epsilon.mb-themes.com/for-sale/computers-hardware/acer-predator-geforce_i70
(view-source shows the same duplicate og:title/og:description/og:site_name/og:type pattern, in the same order, as our site)

We also tested with Facebook's Sharing Debugger (developers.facebook.com/tools/debug/) on our own listing URL. It doesn't consistently pick one block over the other — it mixes fields from both sources: og:type="product" came from the core block, while og:title and og:description came from the theme block. The resulting link preview is therefore an unpredictable combination of the two, not a clean either/or.

The likely cause: item.php's own OG block predates OSClass core adding native Open Graph/structured-data support (structured-data.php), and the theme was never updated to drop its own block once the core started covering this. This probably needs a theme-side update to remove or condition the theme's duplicate block so it doesn't collide with core's output.

Could you confirm whether this is a known issue, and whether an Epsilon update is planned to address it?

Thanks

*

MB Themes

Thanks for feedback, we will be updating themes one by one to fix this problem.
  To get fast support, we need following details: Detail description, URL to reproduce problem, Screenshots