Hey @Richard,
Thanks. Yes, it's working. The only issue is that the necessary delay of setTimeout is a guessing game. Because layCarousel.initModule(), which calls new Swiper(), itself gets called on newpageshown().
Feature suggestion: It would be nice to have another event exposed that runs once the carousel (or all addons) are initialized. That way we wouldn't have to rely on setTimeout to access swiper. In the case of Swiper, it could use https://swiperjs.com/swiper-api#event-init.
Hey @mariusjopen,
Does anything speak against an approach like this, invoking https://swiperjs.com/swiper-api#method-swiper-slideTo?
window.laytheme.on("newpageshown", function(){
setTimeout(() => {
const swiper = document.querySelector('.swiper-container').swiper;
swiper.slideTo(randomIndex, 0, false);
}, 50);
});
Use the following custom CSS and JS to adjust the appearance and behaviour of the desktop menu. You can see it in action on https://quantaviva.ch
Custom CSS for Desktop Version:
nav.laynav.primary:before {
display: block;
content: "–––\A–––\A–––";
white-space: pre-wrap;
line-height: 0.6em;
font-weight: 900;
cursor: pointer;
}
nav.laynav.primary.toggled:before {
content: "✕";
font-size: 1.5em;
line-height: 1.15em;
}
nav.laynav ul {
display: none;
width: 96vw;
background: #fff;
}
Custom <head> content:
<script>
jQuery( document ).ready(function( $ ) {
$(".laynav.primary").on("click", function(e){
$(this).toggleClass("toggled").children("ul").toggle();
});
});
</script>
Hey @Richard, any news yet on the issue? Or might it be an option to downgrade to an older version? If so, could you provide us with a ZIP.
Hi @Richard
Can confirm that we've tested all the conditions you listed. The error persists.
Best,
Brogr
Since a recent Lay theme update our site https://dominikbachmann.com (user & pw: 0000) is no longer working on mobile (desktop works fine), due to fatal JS errors that occur both on load and on menu click:
ON LOAD error:
Uncaught TypeError: Cannot read properties of undefined (reading 'currentStyle')
at HTMLDivElement.<anonymous> (frontend.app.min.js?ver=4.1.0:1)
at Function.each (jquery.min.js?ver=3.6.0:2)
at S.fn.init.each (jquery.min.js?ver=3.6.0:2)
at ao (frontend.app.min.js?ver=4.1.0:1)
at Object.initModule (frontend.app.min.js?ver=4.1.0:1)
at Object.<anonymous> (frontend.app.min.js?ver=4.1.0:1)
at n (frontend.app.min.js?ver=4.1.0:1)
at frontend.app.min.js?ver=4.1.0:1
at frontend.app.min.js?ver=4.1.0:1
ON MENU CLICK error:
frontend.app.min.js?ver=4.1.0:1 Uncaught TypeError: Cannot read properties of undefined (reading 'find')
at HTMLAnchorElement.<anonymous> (frontend.app.min.js?ver=4.1.0:1)
at HTMLDocument.dispatch (jquery.min.js?ver=3.6.0:2)
at HTMLDocument.v.handle (jquery.min.js?ver=3.6.0:2)
Perhaps including other Lay options too, e.g. footer:
<wpml-config>
<admin-texts>
<key name="theme_mods_lay">
<key name="frontpage_select_page" />
</key>
<key name="lay_projects_footer" />
<key name="lay_pages_footer" />
<key name="lay_categories_footer" />
</admin-texts>
</wpml-config>
@mariusjopen Would be handy to have this solution included in the Lay Documentation. I can confirm that it works.
@nypaloto said in Lay Theme and Polylang_Front Page:
Got this solved, thanks to Polylang's support:
- Create a 'polylang' folder in wp-content (or use existing 'polylang' folder)
- Upload the wpml-config.xml file (see below link) into the 'polylang' folder
- In your Wordpress admin, go to to Languages > String translations and search for 'frontpage_select_page'
- Replace the existing number in the ID field of the foreign language with the ID number '112' (see screenshot received from Polylang in below link )
- Save the changes
And this should do it! It worked for me, with a site in English and Japanese. Note that we're using Project Thumbnails for our home page (not Thumbnail Grid or Element Grid), and had to manually add the Japanese thumbnails to the Japanese home page.
XML file and Polylang's screenshot are here: https://drive.google.com/drive/folders/14kQ_7C6hEwktKLXzmAYcBwAzm8lSl_gi
Hope this helps!
@mariusjopen That's the idea...
Hi @heleneleuzinger
You'd find most of the relevant CSS code in frontend/style_phone.php: look for .mobile-nav and the relevant mobile-menu-style. As I said, this solution isn't ideal, as lay upgrades might make your custom CSS code faulty.
The more stable approach I'd recommend is to use custom CSS and JS to adjust the appearance and behaviour of the desktop menu itself...
Best
Hi,
When I set a link on a row background in a category on a website that's installed in a subdirectory, the permalink on the frontend HTML output is missing the subdirectory. The link nevertheless works in JS, but it's wrong in the HTML output, which means opening it in a new tab/window results in a 404.
You can see this happening on the home page of http://clients.ateliervarga.ch/nz/
Best,
Brogr
A less messy way is to use custom CSS and JS to adjust the appearance and
behaviour of the desktop menu itself. I've done this here: http://clients.ateliervarga.ch/nz/
It's possible but messy. You can hide the desktop menu in the Customizer and copy the CSS code pertaining to the mobile menu from the laytheme files into the custom CSS desktop code in the laytheme options to render the mobile menu visible on desktop. I've done this here: https://annafrei.net/
Generally it works well but the critical problem is that laytheme upgrades often render the custom code obsolete, which then needs to be painstakingly updated.
Hi Armin,
https://2019.nomadicarchitecture.ch/projects/world-exhibitions-of-telecommunications-geneva/ is a category, not a project.
The project is https://2019.nomadicarchitecture.ch/projects/world-exhibitions-of-telecommunications-geneva/ibm-telecom-geneva-1-world -- but it's concerning all of them, so you can click on any of them.
Alright, sent you an email.
Actually, this isn't working properly yet: When you access a project directly through the URL (rather than through JS via the menu), the parent menu item only gets the class current-post-ancestor but not the current-menu-parent one, resulting in the submenu being invisible. Could you please look into this again?
I second this feature request: would very much like to use captions AND circles too.
@arminunruh Great, thank you Armin. It's working well!