Posted: January 4, 2022 at 12:33 pm
Original thread: https://eventespresso.com/topic/user-is-created-in-wordpress-on-registration-although-reg-form-option-is-no/ I’m having a similar issue with the WP integration. I have Default setting for Login Required on Registration set to “NO” but it’s still requiring a log-in. |
|
Hi Heather, I’ve split your reply into its own thread as this sounds like a different issue. Just to confirm, is it this that you see currently asking to log in? https://eventespresso.com/product/eea-wp-user-integration/#traffic-cop |
|
Hi Tony, I also have another question on the WP Integration. When registering more than one attendee I also get the following error: Here’s a screenshot. |
|
Ok, so the login required option is different from what you see above (that’s the ‘traffic cop’). When Event Espresso is set to require a login it forces everyone to log into the site to register, as in if you don’t have an account you can register at all. The traffic cop feature is a way for Event Espresso to know for sure which user the registration is for, it can be disabled (an needs to be for your request above) but just to be clear when that option is disabled it can me the registration is not linked to the user and will not show up in the ‘My Events’ section for that user. EE will make the best guess for who the registration should be linked to and generally that will work just fine, but I’m just letting you know of a side effect of disabling that function to be aware of. To disable the traffic cop you need to add a snippet of code to your site: https://gist.github.com/joshfeck/1131145859a3fab58f4d#file-disable_email_match_everyone-php You can add that to a custom functions plugin on your site, we have some documentation on creating one here: https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/ |
|
Thanks Tony! |
|
You’re most welcome 🙂 Any further questions just let us know. |
|
Hi Tony, our developer has added the code to both our dev site and our production site. Disabling the traffic cop worked perfectly on dev but not on production. What are we doing wrong? |
|
What happens on the production site? Where are you adding the code? |
|
I’m getting the same error as before the code was added to disable traffic cop. Here’s a screenshot. https://prnt.sc/264u9ed |
|
Is it the same snippet in exactly the same location on both? When testing both are you logged in? I need more details on what was used and where to be able to answer, but my guess right now is your developer is using this first snippet from my gist and they actually want to be using the section (the one I linked to) |
|
Hi Tony, I’m Donaldo, i added the snippet code on functions.php, same locations on dev and production: https://prnt.sc/26jsmfd also, we are getting this warning, not sure fi this is related but it comes from one of the EE add-ons: https://prnt.sc/26jsmyd |
|
Ok, don’t add the code to Use a custom functions plugin: https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/ Also, the snippet you are using is the ‘first’ snippet in the gist. That snippet disabled the Email Traffic cop check only when logged OUT, is that what you want or do you want it disabled for all? If you want it disabled for all, use the original snippet I linked to: https://gist.github.com/joshfeck/1131145859a3fab58f4d#file-disable_email_match_everyone-php Meaning you swap out the above for use:
|
|
Tony, We created a custom plugin adding that code and we got the same results, it’s not working, is it possible to have a quick Zoom call for support? |
|
The above code completely disables the check, if you’re still getting exactly the same error then the code from above isn’t running. Rather than a zoom call, can you send me the credentials for the site so I can take a look? If so you can use this form: https://eventespresso.com/send-login-details/ Note I’ll need a list of all of the steps you are taking to reproduce on the site. Zoom calls are great but not when I need to view the code, it’s quicker and easier all around to view it directly. |
|
I sent the requested credentials using the provided link |
|
Thank you, so I checked this and the code is working as expected. When logged in on the site the details are checked, if a user is found matching the details you enter it will show the message. When logged out the details are not checked and will allow all registrations. I tested this using the credentials you sent and the above happens on each test. Right now the site is indeed using the using the first snippet from above as mentioned HERE. If you want to disable the check completely then you need the single line of code I added in that replay. I’ve also added it to your custom functions plugin (although commented out so right now it does nothing) so you can see it on the site. |
|
Tony, I’m still getting this error. https://prnt.sc/26ni8m9 |
|
Are you logged in or out? |
|
Logged in. |
|
Then again, the code is working exactly as it should.
Swap the code in use on the for this single line:
That completely disables the check when both logged in and out. |
|
I didn’t make any change to the code running on the site, I added a comment to the plugin. If you want me to swap that code out for you I’m happy to do so? I assumed your developer would prefer to do it so they knew what was happening. |
|
The support post ‘Split: User is created in WordPress on registration although reg form option is No’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.