Home Forums Event Espresso Premium Split: User is created in WordPress on registration although reg form option is No

Split: User is created in WordPress on registration although reg form option is No

Posted: January 4, 2022 at 12:33 pm

Heather Jones

January 4, 2022 at 12:33 pm

Original thread:

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.


  • Support Staff

January 5, 2022 at 3:41 am

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?

Heather Jones

January 5, 2022 at 7:16 am

Hi Tony,
Yes, it is saying to log in when I have it set to “login not required”.

I also have another question on the WP Integration. When registering more than one attendee I also get the following error:
“You have entered an email address that matches an existing user account in our system. You can only submit registrations for your own account or for a person that does not exist in the system. Please use a different email address.”
Both attendees work for the same company and both have WP user accounts. Attendee #1 is signed in and registering for a colleague. How can this be done without getting the error. You obviously can’t be signed in as 2 people.

Here’s a screenshot.


  • Support Staff

January 5, 2022 at 7:45 am

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:

You can add that to a custom functions plugin on your site, we have some documentation on creating one here:

Heather Jones

January 5, 2022 at 8:49 am

Thanks Tony!


  • Support Staff

January 5, 2022 at 11:06 am

You’re most welcome 🙂

Any further questions just let us know.

Heather Jones

January 20, 2022 at 8:58 am

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?


  • Support Staff

January 20, 2022 at 9:15 am

What happens on the production site?

Where are you adding the code?

Heather Jones

January 20, 2022 at 2:16 pm

I’m getting the same error as before the code was added to disable traffic cop. Here’s a screenshot.
However, it works fine on the dev site. I’ll asked the developer where he added the code on the production site. Any ideas why it would work on dev and not in production?


  • Support Staff

January 20, 2022 at 2:42 pm

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)

Heather Jones

January 26, 2022 at 2:17 pm

Hi Tony,

I’m Donaldo, i added the snippet code on functions.php, same locations on dev and production: also, we are getting this warning, not sure fi this is related but it comes from one of the EE add-ons:


  • Support Staff

January 27, 2022 at 3:20 am

Ok, don’t add the code to functions.php as load order complicates things.

Use a custom functions plugin:

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:

Meaning you swap out the above for use:

add_filter( 'EED_WP_Users_SPCO__verify_user_access__perform_email_user_match_check', '__return_false' );

You must be logged in to reply to this support post. Sign In or Register for an Account

Event Espresso