Rik

That seems like an awful lot to shutdown on a live site, for one field that doesn’t get its value sent.

I will first check what information is inside the array upon the mailsent event. Because when I add any field there’s no problem, until it’s a select field.

Don’t get me wrong, I read your reference, but can’t pull the site offline atm.

I will report back if it doesn’t work, or when I disabled the theme and plug-ins.

Several, listed below.

to point out, the subject ‘field’, when filled, is getting sent. it’s only the ‘select’ that doesn’t.

Theme:
Generatepress
Plugins :
Wordfence, WP Fastest Cache, Rank math, Code snippets, Contactform 7, Flamingo, Lightweight Social Icons, Generateblocks (Generatepress), Simple Google reCAPTCHA, Smart Slider 3, Elementor (pro), Rank Math SEO, WP Mail SMTP

Thanks for helping out

to add to this it may be important to mention.

when submitting the form it doesn’t matter if i ‘touched’ any of the options. this happens without me actually clicking something in the select box, and happens also when i keep it on default 1

Hi Peter,

Thanks for your elaborate response.

Just for my information, are the IP addresses you’re whitelisting for 2FA definitely confirmed as static IPs?

Yes, the IP’s are confirmed since I also use my home IP to host other things that need to be accessible from the web. Those are confirmed, also with the site you suggested. So there is no reason for me to think they’re wrong, but I double-checked anyways ??

If the above doesn’t give us any solid reasons why this is happening, can you send a diagnostic report

I’ve just sent the report from diagnostics using this forum’s username: @rikdol.

so in the console, you’d be wanting to look for red Javascript errors, or the network tab reporting any failed page loads.

I can’t see errors in the console during the login phase.
After entering the username/password it will prompt me for the authenticator code. Which is tedious when I’m working from home.

I responded a bit late since I didn’t get notified of a response. ill be watching the thread more closely ??

het probleem is vanzelf opgelost, mogelijk een fout in cache van chrome ondanks ctrl+f5.