Hoping someone can shed some light on an issue I’ve been having with a module and landing pages. I’m utilizing a module that has several content options, such as an accordion and modal pop up button. When I implement this module on our webpage template, it works perfectly fine. However, once it’s used on our Landing Page template, the js for both the accordion and modal pop up doesn’t fire. Both the webpage and landing page template use the base.html boilerplate with the caveat being '{% block header %} {% global_partial path=‘./partials/header-landing-page.html’ %} {% endblock header %}’ being used in the landing page template so that it hides our main navigation and replaces it with the standard landing page header.
I’ve realized it is this {% block header %} that is causing both the accordion and the modal pop up to not fire. Any suggestions on how I could get around this?
It’s really hard to tell what’s causing this issue based on the details you have provided. Please share more details like the code snippet or the page’s URL if possible.
Both pages are using the same base.html template but the Landing Page template has:
{% block header %}
{% global_partial path=‘./partials/header-landing-page.html’ %}
{% endblock header %} - in order to hide the main nav on Landing Pages
Thanks for the reply Teun. The difference in URL is because the LP is a staging link as I didn’t want to place the test page on our production side. I have checked off jQuery and it still made no difference. I can’t figure out what the file isn’t firing
I would suggest keeping the jQuery option checked on and using the 1.7.x version.
Are you using a third-party app for your modal?
Looking at your homepage, it looks like you are using a third-party app for your cookie consent modal.
I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!