yes, I guess SOME users are reading that and some of those are actually doing it- But it is still frustrating for our treasurer so I'm still tasked with trying to find the root cause and fixing it.
Of course, we want to get to the root of the problem. What I wanted to know was if it was the double clicking of the button what could actually be causing the double transaction, or if it was sometihng else happening afterwards. That's why I wanted to confirm that less users clicking twice actually seemed to reduce the number of times this happens.
to turn on logging...I didn't want to do that without checking with you first after reading all the caveats and warnings on that page
It's fine to have it on for troubleshooting, that's its purpose. The warning is there because it stores some data that you may not want others to see, in case someone breaks into the site. Just delete the log files after you're done using them.
I setup a test sub-domain and can easily clone our prod site over to it with UpdraftPlus so was thinking it might be possible for me personally to replicate the error after turning on the logging there. But I think s2member is licensed to work with only one site, correct?
This is perfectly fine, the single-site license refers to production sites, staging/development is fine and you can have all you need.
If you can reproduce the behavior in the tests clone, that's good enough for troubleshooting.