hey thx i saw your email. i cant access that site, you can send me your ftp login to info@laytheme.com it just shows a 500 error

Thank youu

Thanks @arminunruh I got to the bottom of it. User error. The site was using page overlays for all content pages, and we were positive that we had a footer page setup, but it was in fact built into the single home page layout and not as a seperate footer page. So it's all good, there is no bug relating to this.

sorry about the delayed response, i answered you in your other post <3

seems like an incompatibility with my code and your css for hiding the mobile menu on the frontpage should work with the next lay update!

there was some code that was incompatible with php 7. but i changed that now so it is.

@arminunruh glad to hear all is fixed. the new UI is pretty slick!

ok will be fixed with the next update

Thank you!

[image: image.png] will be part of the next update!

The issue currently with iOS 26 is if we have a fixed overlay (like the intro is) or a mobile menu (if it's browser height), it actually never covers the bottom part anymore under the glass UI of Safari. Even if I set the height of a fixed browser height container much bigger, it never covers that bottom part. It's always an empty gap there. If you go to apple.com and open their mobile menu, you see they somehow coded a workaround where the bottom part will just become black. But as you can see, when you close the mobile menu, that part then just stays black. Which is kind of weird. I will try to find out how they did it and implement this workaround, but if I do that, you will just have a white bar at the bottom of your browser window instead of the see-through bar.

thanks! i fixed it on your site. And the fix will be included with the next Lay Theme update too!

ahh ! now i understand. yea the mobile menu does not support multiple menus. but the way you did it is clever yep.

With this code, .row.rowcustomheight .row-inner{ position: relative; } .row._100vh .row-inner{ position: relative; } The X-Y percentage offset follow the 100% with container, not considering max width [image: Screenshot 2025-10-22 alle 13.07.40.png] Not a problem for me yet, i ll wait for your update, please consider this

i think i saw this before. its either this: https://support.google.com/chrome/thread/160423794 or its a browser extension that does that: https://support.google.com/chrome/thread/158842932/why-are-random-white-boxes-appearing-on-various-sites-within-my-chrome-browser?hl=en

Thank you so much! It runs perfect now <3

Oh hey, I see. I think we already emailed about this, so just use a value like 90vh instead of 700px for the fixed height.

Hey there, that's interesting. So when I look at this on WhatsApp, it looks right. But when I look at it on iMessage, the situation is like you described. looking at whats linked in the metatags i see: https://i0.wp.com/arthurfoliard.com/wp-content/uploads/2025/04/Amazon_CS_15_Outro_01_Overview.jpg?fit=1200%2C675&ssl=1 there is actually no reason for iMessage to show it twice. This could very well be a problem with the iMessage service xD

ah yea ure totally right! ok working on a fix now