Seemingly rare RSVP form submit problem in Chrome?

I doubt Chrome is the problem. Can you reproduce the problem yourself? Might help if you shared a link to the specific event this issue is associated with

I doubt it is too. I cannot reproduce it myself yet. It’s not the specific event page as this is a problem she has with any of the events. This is the first we’ve heard about it from a site visitor, though that often doesn’t mean much. The only time I’ve seen anything remotely like this behavior with Chrome is when a URL is sent to it from certain flavors of application code (e.g., a user action in the application calls code that opens a URL, and Chrome is their default browser) where that opened URL has variables passed through in the URL itself. For security reasons, it would (at least in the past – haven’t checked in a while) truncate the variable parts and just leave the typically-formed URL, which didn’t work because the page needed those variables. I can’t imagine that could be related to what you’re doing here, as I skimmed the plugin code and it looks like the normal stuff you would expect to be happening. Do you have any knowledge as to whether any Chrome security extensions would do anything to mess up variables passed through a URL upon a form submit like what you’re doing here? I honestly have no idea and am just thinking out loud. It’s quite likely not worth the time spending hours debugging this, but I was just wondering whether you or anyone else had ever heard of something like this. Thanks!

I haven’t completely tested all this, but here’s what I discovered. In Chrome/Windows at least two of the events generated off a particular template creates the following URL when you submit/post – https://ourdomain.org/?post_type=rsvpmaker&p=2079 (which obviously doesn’t do anything). Another event based on a different template generates this URL on submit, which does work – https://ourdomain.org/rsvpmaker/orientation-2017-7-18/?e=myemail%40mydomain.com&rsvp=282 – and I entered the same information in the forms in both events.

I have been staring at the two templates and events for over an hour, down to inspecting elements in my browser – and can’t find any difference at all between the two. Based on how it behaves, I’m assuming there’s some listener than builds the URL based on user input and performs actions when the thing with that submit button’s ID is clicked. I can’t really give you access to the events as they are behind a password wall. My only guess is that there’s something that got messed up or corrupted when I created that template. If I made some small, insignificant change to it, updated the template, and propagated the refreshed template through all the existing events, would that potentially rebuild everything and do something with whatever about this broke?

I think I figured out a workaround at least. I went on our private test server that has a mirror copy of the website, deleted all the future events based on that particular template, and then I just had the template regenerate those future events (they occur monthly on a schedule). That actually worked. So I have no idea what got corrupted the first time I generated the events, but redoing it appears to have fixed it. Not sure if this helps you or not, but I at least wanted to share all this if it does.