Just completed a new fetch with v12 and now the paths for bestiary images look borked? #23
-
|
Beta Was this translation helpful? Give feedback.
Answered by
ebullient
Oct 16, 2022
Replies: 2 comments
-
oh! I should make another note! If you're using a custom template, the token structure has changed. That's my fault, I should have done this compatibly. I've added notes here, does that help? Should I add more? |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ebullient
-
Perfect thanks!
C
…On Sun, 16 Oct 2022 at 20:38, Erin Schnabel ***@***.***> wrote:
oh! I should make another note!
If you're using a custom template, the token structure has changed. That's
my fault, I should have done this compatibly.
Update your template to use something like this (instead of the single
token string):
{#if resource.token}
![{resource.token.caption}]({resource.token.path}#token){/if}
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABL7VCE3MTPTUKC55TNT3H3WDRKT5ANCNFSM6AAAAAARGMYOI4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
oh! I should make another note!
If you're using a custom template, the token structure has changed. That's my fault, I should have done this compatibly.
I've added notes here, does that help? Should I add more?