I’ve been pasting in URLs into the panel for article text and making sure they are converted from HTML into Markdown.
Sometimes the URLs for a link contain a closing parens and this results in the (link: improperly closing after the parens.
Any thoughts on this? I’ve created an issue for the wonderful Kirby Markdown plugin which I’m using but it’s possible the problem also exists outside of the plugin. https://github.com/sylvainjule/kirby-markdown-field/issues/79
My workaround is to simply use standard HTML instead of Markdown for these occasions.
This is a big issue, imho. Clients will want to use parens in the link text, too. I would love to use standard markdown links, but is it possible to reprogram the link button in the WYSIWYG editor to do that, too?
@yatil Yes, those cases are not easy to handle, there are certainly workarounds, e.g. let users use square brackets and replace with a kirbytext hook afterwards etc. But that requires educating users, of course.
When I put my Twitter plugin together, i needed a way to turn links into clickable links, since the Twitter comes back with tags stripped. Theres a function in that plugin, i forget where i found it. The reason i bring it up is that it wouldn’t take much to borrow that function and turn it into a field method.
That way you just paste the url straight in the field without using the Kirby tag, and the field method will link it up. As for link text, im not sure how you would handle that, you would need to expand the function a little.
You can disable kirbytags in the Panel in your config.
'panel' => [
'kirbytext' => false
Kirby will then insert standard markdown syntax instead of Kirbytags.
You will lose the additional options you can use with Kirby’s link or image tags (adding classes, captions etc.). So while yes, tags are in a way a regression compared to standard markdown, they also have a lot of advantages.
You can do that anyway and markdown/kirbytext will parse it without any additional functions. But the problem here is the link text, or the combination of link + link text + additional attributes like classes etc.
I guess what is really needed here is a way to change the charachters that kirby uses to detect the tags, so you can do [link: ..] or something, but i bet sooner or later that will upset some other kind of link for something else. You would have to pick a charachter that wasnt legal in a URL.
Exactly. I can’t find it now, but we had this discussion already back in Kirby 2 or even Kirby 1, trying to find a pattern that would allows parentheses, but it never lead to anything.
Additionally, there’s the problem with backwards compatibility…
IMO, the easiest way to solve this is by asking users to use square brackets instead of parentheses if they absolutely need to use them in Kirbytags, then replace with a filter. Or, if you can do without the additional features offered by tags, disable Kirbytags in the config and use standard markdown instead.
What if the new way that kirbytext understands a link is by determining if it has an open parens in the link, and automagically understanding that there might be a closing parens, too? And then behind the scenes encoding it as such. This would bypass this rare (but painful) issue of educating clients.
Until then, it’s not the end of the world for this problem to exist, and it is, indeed, an edge case. Thanks everyone.