- Status changed to Needs work
almost 2 years ago 5:40pm 10 March 2023 The last submitted patch, 2: html-title-warnings-3278540.patch, failed testing. View results β
- First commit to issue fork.
- Merge request !24#3278540 Added sanity check in views field handler β (Open) created by quadrexdev
- Status changed to Needs review
8 months ago 3:37pm 9 May 2024 - πΊπ¦Ukraine quadrexdev Lutsk
Moved the changes from #2 in a merge request, and all tests passed.
- First commit to issue fork.
- Status changed to RTBC
8 months ago 2:51pm 12 May 2024 - πΊπΈUnited States generalredneck
So I was trying to reproduce this issue. It seems that there's another issue at play here that actually seems to render the code in the if statement moot anyway because we are checking for
$this->options['settings']['link_to_entity'] === TRUE
.The problem here is that
$this->options['settings']['link_to_entity']
is in fact the number 1 instead of the boolean TRUE
Given that, we need to fix that check so this can be reproducible. Given that, Immediately looking at the code I can see that prior to this fix,
$alter['rendered']['#title']['#context']['value']
was always created and always a string or Markup object because of$this->htmlTitleFilter->decodeToMarkup()
always returns that type. With this fix, that array item doesn't exist and "may" cause unexpected side effects, but I don't know that for certain. It also seems like this would only ever happen if for what ever reason the "title" was empty some how from upstream.No amount of me messing around with a node and view settings in the UI got me an empty value there. So I have to assume that this has to be on some other type of entity and possibly a broken view configuration?
Given that, after fixing the check in the patch, I'm not receiving any bad side affects. I would feel much more comfortable with steps to reproduce this and/or a view this happens on for us to inspect. However, given the realtivly simple nature of this fix, I'll go ahead and mark it RTBC