Noparse issue with markdown fields

[riasvdv]

Bug Description

I have a markdown field with the following contents:

{{ color.label }}

This is what gets output when I dump the field in my templates:

<p>noparse_56c56f2a2936bb9da06452fbd043aec8</p>

The final html however is just

<p></p>

Seems like the {{ color.label }} is somehow being parsed.

Environment

Statamic version: 3.0.0.-beta-41

PHP version: 7.4

Install method (choose one):

• Fresh install from statamic/statamic

[jasonvarga]

Are you using vue or something similar on the frontend?

Is that <p> empty in the actual rendered source?

[riasvdv]

So this is the field:

This is what's rendered

When I | dump the markdown, this is shown

Just using a normal antlers partial

<div class="max-w-3xl mx-auto my-8">
    {{ markdown }}
</div>

[riasvdv]

It's a set inside a Bard though, if that maybe helps

[jasonvarga]

Can you confirm that you are looking at the rendered html output (using "view source") rather than devtools?

[riasvdv]

View source also has an empty <p>

[riasvdv]

Ah no, sorry, it's just an empty div

The <p></p> is from Bard

[jasonvarga]

So it's correct?

[riasvdv]

No, when I type {{ color.label }} inside a markdown field, I expect to see this html:

<div class="max-w-3xl mx-auto my-8">
    {{ color.label }}
</div>

It shouldn't try to parse what I type inside the markdown field

[jasonvarga]

Yeah ok sorry haven't finished my coffee. 😅

If you have some other text in the markdown field, you see that, right? Just not the {{ color.label }} part?

[riasvdv]

Yes

Result:

[jasonvarga]

Can you paste the yaml for that field in your blueprint?

[riasvdv]

Sure, it's just the default Markdown one inside a Bard set

markdown:
              display: Markdown
              fields:
                -
                  handle: markdown
                  field:
                    restrict: false
                    automatic_line_breaks: true
                    automatic_links: false
                    escape_markup: false
                    smartypants: false
                    type: markdown
                    localizable: false
                    listable: hidden
                    display: Markdown

[mattmurtaugh]

I'm pretty sure I'm have the same issue. It looks like there was a change with how markdown is parsed and it no longer parses any variables or tags within the content.

We use this a lot for things like {{ company:phone }} or {{ company:email }} in blog posts of pages to reference the global variable. I can't say for sure this ever worked in v3, but I heavily used it in v2.

I also have a special use case where I've created at widget tag that I can use to display widgets inside a blog post like this {{ widget:game from="job-simulator" position="left" }}. I know for sure this one worked because I wrote the tag specifically for v3. The tag works on its own in a template, but not if used within markdown like it used to.

Statamic version: 3.0.0-beta.46
PHP version: 7.4.6

[jasonvarga]

Matt, you need to add antlers: true to a field to have it parse variables inside markdown. Sounds the opposite to the issue Rias is describing.