Fatal error after updating to toc_api:^2

Can confirm issue, patch from MR14 worked flawlessly.

@fjgarlin Unfortunately, I was confirming too fast that MR14 worked. As it turn out, I could place the TOC block in block-layout without throwing an error message, but then there is no TOC block displayed. Using automatic placing or via token [toc] works as expected.

That might be a separate issue. The change in this MR is purely for the "Fatal error" issue.

I also confirm that the patch fixes the fatal error, but the toc block is missing. Moreover, the toc_api seems to have an issue on LB as well, so I don't know if the missing block is due to a bug in toc_api or toc_filter. I'm investigating.

It seems that toc_api (specifically the TocBlockBase class) has an issue with Layout Builder. The getCurrentToc() method returns a null value. Additionally, the getCurrentNode() function checks the route name but doesn't account for Layout Builder paths.
I've reported the issue on the toc_api module: https://www.drupal.org/project/toc_api/issues/3520464 🐛 Layout builder fatal error Active

Thanks for this, just noticed this now, I'll review this asap.

Ah , looks good, unfortunately I'm not the maintainer of this project.

Adding patch from PR here so I can use it in my project.

Postponed on upstream toc_filter fix being merged/tagged/released.

What has to be released? The latest toc_filter 8.x-2.x is tagged and released as 8.x-2.3.

🐛 Layout builder fatal error Active
is needed.

I don't understand. The comments in 🐛 Layout builder fatal error Active say to apply the patch in this issue.

haha, true RTBC for this.

Thanks, all. Committed. 🍷

Automatically closed - issue fixed for 2 weeks with no activity.

#3520464-14: Layout builder fatal error →

There's a report from someone stating.

should we reopen this issue, as it isn't really fixed in my opinion

I think that the reported error is different from this one (this one was only about the blockAccess method return type), so a follow-up issue, different from this one, is probably better in my opinion.