I saw that calling markdownify on a string with a partial (inside a shortcode) makes makes the frontmatter inaccessible from within the hook.
I don’t it is intuitive at all for the user. I think page parameters should always be visible no matter where the code runs down the line. It shouldn’t devour CPU or memory to ensure that.
I have no idea what this is about.
This seems to have nothing to do with partials, but with markdownify vs .Page.RenderString. And it is a transient bug as well, as I saw it changes in front of my eyes thrice after deleting a completely unrelated content file.
It made replicating it very difficult since I don’t know what you’re gonna receive. Last time I tried the following the bug was still there. You need use the menu and go to the only exercice in section II (I remove everything else).
all v and b are supposed to be the same color: pink. they were not.
Before when copying the exact same content in the homepage, it wouldn’t replicate, so it’s place-dependent too. But I won’t modify anything more in fear the bug ceases.
I can’t deal with github now: so be my guest with this: repo.
This really tried my patience… If it doesn’t replicate with you, then to hell with it.
hugo v0.154.5 linux/amd64 BuildDate=unknown