Hi,
we also run into the exact same error that broke the functionality of some custom filter buttons on a page of our website. So far, I don’t quite understand from the answer how the error might be related to the template in use.
In our case, if you open the linked source file from the error message in the browser console you can see that the element which is registered to the event listener is null , thus registering the event listener fails. So, for some reason, registering any additional event listeners also fail.
If I try to access the email element from the console using the code from the source file:
const email = document.getElementById("email");
the return value is always null. Where does the element with the id “email” suppose to be present in the DOM?
All that being said, we were able to fix our problem by wrapping our custom code in a window.onload() function and our event listeners do now work again, but the error is still being logged on every page you navigate to.
-
This reply was modified 9 months ago by zollillo.
