πŸ‡ΊπŸ‡ΈUnited States @jlancaster

Account created on 30 June 2010, almost 14 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States jlancaster

Confirming patch #5 addresses 8.3 deprecation notices I was experiencing when testing.

πŸ‡ΊπŸ‡ΈUnited States jlancaster

I have also reviewed the pending merge request changes on a D10.1.6 site of mine that depends on bfd and confirmed the upgrade to D10 is successful and no errors/regressions are present.

πŸ‡ΊπŸ‡ΈUnited States jlancaster

Thanks. 2.3.1 release fixed the console error related to library and all is good now. Never had issues with library being found in status report so I can't speak to that being resolved or not.

πŸ‡ΊπŸ‡ΈUnited States jlancaster

Same symptoms here as #7. Status report is clean but the "keyword var" error pops up in js console. Forcing downgrade to 1.6 or adding semicolon fixes.

πŸ‡ΊπŸ‡ΈUnited States jlancaster

In my opinion, the issue is different because #2980299 is related to the UX components and the destructive action as you perform it. In this case, I cannot find a way to expose UX elements for the element within question (menu_link_content.layout_builder__layout) to work with it and purge data.

The simplest explanation would be that I'm simply overlooking where this could be but I have dug and dug without any success, which is why I came here and referenced the other issue because it is "kind of close but not quite" to this particular issue.

I keep asking myself: "If there was a page to manage menu displays, where would it be?" -- I have never seen such a thing. But maybe layout builder had one at one time way back when?

Production build 0.69.0 2024