I have a surprisingly difficult time to make Kirby show the respective tags of a single blog entry. The tag itself should, of course, link to a page with other tagged articles.
This is how the core of my blog homepage looks like:
This functionality has been broken by the latest update 2.3.0. The tags themselves are still displayed correctly, the links, however, lead to empty pages.
To be honest, the changelog overwhelms me. How am I to modify the code?
Ah, it’s the obvious things I forget, thanks for the hint! Here’s what I get when I open the tag-specific page:
Fatal error: Uncaught Error: Call to a member function url() on boolean in /kirby/kirby.php:301 Stack trace: #0 /kirby/toolkit/helpers.php(270): Kirby->{closure}() #1 /kirby/kirby.php(678): call(Object(Closure), Array) #2 /index.php(16): Kirby->launch() #3 {main} thrown in /kirby/kirby.php on line 301
Yes, it does. It displays the blog correctly, and single-article pages work as well. The only plugin I use creates the RSS feed, and there are no page models. Apart from the tag features you taught me here, there shouldn’t be anything unfamiliar.
I don’t know, is it possible that the update (via git) had a few glitches? I’m trying to re-set everything up… (Edit: Mh, didn’t work out as well.)
Whoops, the footnotes were from a plug-in I used to test very briefly. I have removed all references, the problem still persists in 2.3.0. Sorry for that.
first() helps me to show only the first paragraph of my entry when needed. In my panel, I have a separate form field for it. first() and text() combined are the entire blog entry.
Now, your first point sounds interesting. Am I right in assuming there are redundant parts within my template?
Not sure about that. If I remove the relevant parts from the template, it breaks its basic functionality: creating a new page after five entries and allowing the possibility to filter the blog by tags.
The controller appears to be crucial for the pages that display only one specific tag (’blog/tag:example’). If I remove it, those pages turn blank. With Kirby 2.2.3, that is! So, could it be possible that the controller is what might cause the issue on Kirby 2.3.0?