Bug in the gridder

[telmotype]

@f-albert

Hi Felix!
I'm using Chrome.

I'm using the following plug-ins for WP:

And I'm using WhatFont and WindowResizer plug-ins for Chrome.

When the bug happens the only way to get rid of it is to delete the mobile layout and generate it again.

All the best!

[f.albert]

Could you please send the credentials and url to f.albert.work@icloud.com?
I would like to have a closer look at that bug.

Best,
Felix

[Pat]

Hi there :)
I have the same problem. Any idea how to solve this issue?
It occurs using firefox and chrome.

Laytheme is up to date, no plugins installed.
Thx, Best
Patrick

[Richard]

Dear Patrick @Pat

Could you please post a link to your website? :)

Do you have any Third-party plugins installed that when de-activated resolve this issue?

Are Wordpress, Lay Theme and All lay theme's plugins up to date?

Best
Richard

[Pat]

Dear Richard,

this is the website: https://beichert.buero-feuerwache.de/

The bug shows up in the CMS. Do you need the login?
No Plugins installed. I have some custom CSS.

Best
Patrick

[Richard]

Hi Patrick @Pat

Thanks for posting your website, was just curious if any obvious errors were showing in console log,

If you could temporarily remove that custom css, just to be safe and send your website address, /wp-admin/ username and password and a link to this topic to info@laytheme.com?

Will have a look as soon as possible,

In the meantime thank you for your patience & have a wonderful day

Sincerely
Richard

[Pat]

Dear Richard,

thank you very much. I will send you a mail soon.
I removed custom CSS, everything (WP, laytheme, plugins are up to date / deactivated).
So it should have something to do with the latest update.

Thanks in advance.
Best
Patrick

[Richard]

Dear Patrick @Pat

Many others share the same sentiment that it was the last update and hope to get this Bug sorted out as soon as possible!

Best wishes and will keep you updated, apologies for any inconvenience this may have caused in your Website building process.

Richard

[arminunruh]

Hello @Pat
Upon further inspection of the json code that makes up the content of your phone version I saw that the stack element itself had a colspan of 1.
Meaning in theory it should have been only 1 column wide.

However, it spanned all 14 columns, but I guess this lead to the unusual behaviour when resizing and moving the elements inside the stack element.

I'm not sure what caused this bug.
By resizing the stack element itself, everything snapped back to place and now the stack element itself uses the correct colspan value.

I wrote this down and I'll need to try to reproduce what caused the stack to have a colspan of 1 and then see how to fix this.

At the moment i'm focusing on implementing woocommerce, not sure when I'll find the time to work on this but at least you know now how to fix this if you come across the error again.

Have a great day and sorry for the long response time!

[arminunruh]

Ok damn, actually after saving the content, the problem still persists.
Ok I'll work on this now. I'll let you know when this is fixed.