Closed blutack closed 3 years ago
Thanks for reporting this, definitely a bug! For prioritizing: Does it affect the contact form's functionality, i.e. did you still receive an e-mail or did the whole contact JS simply fail?
It does indeed prevent the form from submitting silently, as the event handler for the submit button breaks before it makes the request to Basin. From the user perspective, it looks like you push the submit button and nothing happens.
You could actually cherry pick in https://github.com/Fluxense/osprey-delight/commit/91977b6eae11c0866d0569601a05418d1ab173c1 if you want a quick and dirty fix.
Thanks for clarifying this @blutack!
I fixed it by introducing an additional template check within the contact.js
.
In case you want to test this, please checkout the dev
branch.
Hi @blutack
just a short info: I merged the fixes for the issues you reported to the main branch (among dozens of other improvements). Would be great if you let me know if everything works for you.
Sorry for yet another one.
The exampleSite config.yaml says the following:
However, if you comment it out comments won't work because the template correctly doesn't render the dropdown but the javascript assumes
$('select[name=matter]')
always exists on line 21.I've "fixed it" on my site with the following change to check if there's a matter selection and if not, fall back to an empty string:
matter = $('select[name=matter]') ? $('select[name=matter]').value : "",