Update breaks layout

Created on 10 July 2023, over 1 year ago
Updated 25 August 2024, 4 months ago

I duplicated one of the Gridstack/Native layouts (Default Frontend) and was happily using it with GridStack 8.x-2.9, Blazy 8.x-2.15, and GridStack library 5.1.1. Updating to 8.x-2.11, however, broke my layout. Of course Blazy got updated in the process to 8.x-2.16. All caches were cleared. Any suggestions?

🐛 Bug report
Status

Fixed

Version

2.11

Component

Code

Created by

🇭🇺Hungary Grabby

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Grabby
  • 🇮🇩Indonesia gausarts

    Thank you.

    A rush in release was 2.11. Only me rushed in :)

    Mind testing the latest Blazy Dev as of today for a mo? And see if resolved.

    If still broken, be sure to inform me back, and I'll see to it more deeply.

    Just so I know if the issues still stands?

    Let me know?

  • 🇭🇺Hungary Grabby

    Thanks for the quick response. I tried today’s 8.x-2.x-dev, but unfortunately there’s no change, the layout is still broken. It wouldn’t be a big deal to rebuild it, though it shouldn’t have to happen. One weird thing is Blazy now doesn’t show up on the Available updates page. It’s there – composer show says * 2.x-dev, * dev-2.x – and it’s enabled, but for some reason it isn’t listed on Available updates. The necessary db update said something about entity reference formatting, which is interesting because one of my other problems is that I have an EVA view that I can’t get any Gridstack layouts to display. They display with all the standard layout builder and Bootstrap layouts, but not with Gridstack. Just mentioning.

  • 🇮🇩Indonesia gausarts

    Noted. Thank you for useful info.

    We'll dig out more.

  • Status changed to Fixed 4 months ago
  • 🇮🇩Indonesia gausarts

    I assumed this was fixed with the latest guerilla fixes.

    If still an issue, please try 3.x, and feel free to update the report.

    Thank you.

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

Production build 0.71.5 2024