I’m running into a weird issue with permalinks. None of the permalinks Kirby generates (whether to internal pages, files, whatever) function. The full link Kirby generates to internal pages looks like this: page://tBAAwaHz6QRgx2M3, which I imagine looks right, though I saw on the forum some people’s permalinks seem to be prefaced with an ‘@‘ symbol. Clicking the link generates the following error: Failed to launch '<URL>' because the scheme does not have a registered handler.
Where would I register this handler, and what would that registration entail? This issue was happening when I was developing the site locally, and I thought it would be resolved when I moved it to our server. Right now, however, the site is live on a test domain on my work’s web server, though, and the issue persists.
Those aren’t the permalinks but the UUIDs which are only useful internally in Kirby but no URLs for browsers. Not sure how you retrieved those. You get the permalinks from $page->permalink() or $file->permalink(). This will get you URLs as you’ve seen them with others on the forum.
OK. This is a problem I’m running into using the default Link block. I currently use the toBlocks() method to render the collection of blocks on each page. When a panel user links to an internal page or file using the default Link block, toBlocks() sets the href of the links to the page/file UUID. Is there no way to output a usable href (either standard url or permalink) without iterating through every block and then calling permalink() or toUrl() or some other method on each block of type Link?
There is no default link block. This must be a custom one. Can you share the block snippet and blueprint you created for it?