[SOLVED] Fetch RichText as HTML alway use h1 heading size

I have…

  • Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

We are using the default rich text component to store text which is localizable.
If we ask with GQL for this text in a specific language and formatted as HTML,
all headings are in h1.

Via the inspect tab we can see that the correct level was stored:

The HTML output:

The markdown output:

Expected behavior

The generated HTML contains the same heading sizes as the stored content.

Minimal reproduction of the problem

  • Create a schema with a rich text component
  • Use h1 and h2 in a content
  • Ask HTML with GQL API


  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: 7.12.0


  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

I have searched in Google and on this site for similar documentation or reports but I can’t find anything.

Thx. I will fix that asap.

This topic was automatically closed after 44 hours. New replies are no longer allowed.