After upgrading from 0.140.0 to 0.141.0, and replacing all my tweet embeds with {{< x user=“username” id=“id” >}} I’ve run into another problem when rendering my site:
Error: error building site: render: failed to render pages: render of "/Users/h0bbel/GitHub/vninja/content/post/VMware-Updates-vSAN8-ESA-Requirements.md" failed: "/Users/h0bbel/GitHub/vninja/themes/hugo-bootstrap-premium/layouts/_default/single.html:40:9": execute of template failed: template: _default/single.html:40:9: executing "_default/single.html" at <.Render>: error calling Render: failed to execute template _default/single.content.html: "/Users/h0bbel/GitHub/vninja/themes/hugo-bootstrap-premium/layouts/_default/single.content.html:1:3": execute of template failed: template: _default/single.content.html:1:3: executing "_default/single.content.html" at <partial "bloc/content/content.html" .>: error calling partial: "/Users/h0bbel/GitHub/vninja/themes/hugo-bootstrap-premium/layouts/partials/bloc/content/content.html:11:5": execute of template failed: template: partials/bloc/content/content.html:11:5: executing "partials/bloc/content/content.html" at <.Content>: error calling Content: "/Users/h0bbel/GitHub/vninja/content/post/VMware-Updates-vSAN8-ESA-Requirements.md:28:1": failed to render shortcode "x": failed to process shortcode: template: _internal/shortcodes/x.html:26:106: executing "render-x" at <.name>: can't evaluate field name in type template.TryValue
Obviously it’s related to the shortcode (and removing the shortcodes makes it render), but I’m a bit lost as to how to actually fix the issue. I got the same problem with the old tweet shortcode as well, after updating and I had hoped that replacing them with the new one for x would fix it. Sadly, it did not.
Ah, then I don’t. have to pull more of my greys out trying to figure it out
I have quite a few, amassed over a number of years
❯ grep -R "{{< x" content/* | wc -l
355
There might very well be a 404 somewhere there, but going through that manually won’t be any fun, also that means future 404’s might break this anyway…
Wait until the next release… it will include a fix for this. You will still have errors, but it will tell you the position (page, line, column) of the offending shortcode call.
For now I’m happy with waiting for the next release. My live site is running 0.140.0 now anyway, since upgrading it on Netlify breaks it. For now it’s just my local instance that’s not working. That’s not a problem at all, until I decide to post something new. I could also revert all my shortcodes again, and downgrade to 0.140.0, which works (no fun in doing that, but sed gets me a long way ).
WARN The "x" shortcode was unable to retrieve the remote data. See "/Users/h0bbel/GitHub/vninja/content/post/2015-02-02-great-disturbance-force.md:27:1"
You can suppress this warning by adding the following to your site configuration:
ignoreLogs = ['shortcode-x-getremote']
That’s great, thanks! Should I just leave that there, even when a fix is in place at a later point?