- 🇦🇺Australia mstrelan
This came up as a random triage issue for Bug Smash. I'm having trouble agreeing that this is a bug. Nevertheless, in my opinion, it doesn't seem like the "Title override" area handler is an appropriate use of area handlers.
The AreaHandlerBase is the base class for "Plugins governing areas of views, such as header, footer, and empty text." The title of the view is not one of these areas. Instead the Title handler misuses the preRender method to change the title of the view, which should be out of its jurisdiction.
Another point to support this argument is that you can add multiple "Title override" handlers to the same area (No results behavior). The last one wins out.
It seems there ought to be another way to specify the title when there are no results. Or perhaps there needs to be another way to define "behaviors" (such as overriding settings) rather than hijacking "areas".
Happy to hear arguments as to why this should remain the way it is.
- 🇦🇺Australia pameeela
The views UI has changed since this was created, in a way that helps address this issue. Instead of being tucked away in Advanced, the title override is clearly visible in the page:
So I also think it's not a bug, but for the reasons mstrelan outlined, the current functionality is not ideal. So perhaps a follow up task to modify that?
Although I have to say, in 10+ years of building Drupal sites, I never knew about this quirk of standard install and have never used the title override when there are no results! TIL :)
