# Bug reprot OG fields and Resource path

**URL:** <https://forums.realmacsoftware.com/t/bug-reprot-og-fields-and-resource-path/57240>\
**Category:** Elements\
**Tags:** elements\
**Created:** [August 7, 2026, 10:10am UTC](https://forums.realmacsoftware.com/t/bug-reprot-og-fields-and-resource-path/57240 "2026-08-07T10:10:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tati](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@tati](https://forums.realmacsoftware.com/u/tati)\
**Post date:** [August 7, 2026, 10:10am UTC](https://forums.realmacsoftware.com/t/bug-reprot-og-fields-and-resource-path/57240/1 "2026-08-07T10:10:45Z")

</div>

I bought the CMS and have been working on it with Claude and really like it. I am no wizz, so this is not coming from me but from AI!

Ahrefs flagged broken images and issues with the blog pages. I couldn’t find what the issue was and thought I had set it up wrong, so I left it at that.

I worked with Claude on schema and open graphs, and Claude found the errors.

Bug 1 — {{page.opengraph}} merge tag breaks when a page’s OG fields are empty

Here is Claud’s summary: When a page has no Open Graph values set in Page Settings, the {{page.opengraph}} merge tag (used in the site Template to auto-output OG meta tags) doesn’t fail gracefully — instead of omitting the tags or outputting safe defaults, it produces malformed or broken output that affects the rest of the page’s .

Bug 2 — Resource path duplication for uploaded images

Images uploaded through Elements’ Resources panel and referenced in custom code (e.g. manually-written og:image meta tags, or JSON-LD thumbnailUrl fields) sometimes publish with a duplicated path segment, producing a broken URL that 404s, even though the same image displays correctly when placed via Elements’ normal image component.

Claude found a workaround for me, so it’s not urgent, but I thought it would be good to report here to get it fixed.

Thanks