|
Omar Paloma
|
January 25, 2017 at 4:00 am
I am having a similar/same issue as the user in the thread below, except in their case they are forcing users to be logged in to register. I am not.
For me ‘Force Login for registrations?’ is set to ‘no’ and ‘Auto Create users with registrations?’ is also set to no.
What can I do to fix this as it is preventing people from registering?
https://eventespresso.com/topic/additional-attendee-email-already-exists/
|
|
Josh
|
January 25, 2017 at 7:31 am
Hi Omar,
Is the message saying they already have an account and therefore need to log in? That’s actually not a problem, unless you don’t want them to log in if they already have an account, which defeats the purpose of using the WP User Integration add-on. So you can either deactivate the WP User Integration add-on, or add the code from this gist to your website:
https://gist.github.com/joshfeck/1131145859a3fab58f4d
You can add the above to a functions plugin.
|
|
Omar Paloma
|
January 25, 2017 at 1:14 pm
Thanks. Will try the gist. Regarding not a problem and defeating the purpose.
I have not asked the plug-in to require log in or create users. This issue is not about the primary purchaser but the additional purchasers. Are you saying that it is a feature that if another person wants to buy tickets form someone who already is a user they can’t unless they log in as that user?
If so, that would mean that they only way to purchase tickets after an initial purchase would be for each individual to purchase their own ticket. right?
According to your site
you can give your users a special incentive by offering member only events and tickets. You can also help streamline registration with auto populated form fields. You can optionally create new users when someone registers from the front end.
I thought were using the plug-in as intended. We are trying to offer member-only tickets while still allowing non-members to purchase, albeit at a different price. Isn’t this one of the selling points of the plug-in?
|
|
Josh
|
January 25, 2017 at 1:38 pm
Are you saying that it is a feature that if another person wants to buy tickets form someone who already is a user they can’t unless they log in as that user?
No.
If so, that would mean that they only way to purchase tickets after an initial purchase would be for each individual to purchase their own ticket. right?
No, however, if you’ve set up the system to create a user account when someone registers for an event, that could cause the error you saw, because now they’ve got a user account, and the WP User add-on will prompt someone to someone to log in if they have an account. This is also one of the advertised features described here:
https://eventespresso.com/product/eea-wp-user-integration/#traffic-cop
|
|
Omar Paloma
|
January 25, 2017 at 1:52 pm
Thanks Josh,
To make it clear, we have NOT activated this traffic cop feature and we have NOT set up the system to create a user.
In this case it would appear there is a bug in the plug-in.
|
|
Josh
|
January 25, 2017 at 2:04 pm
The traffic cop feature isn’t something you activate, and what you’re seeing is not a bug. It’s the traffic cop feature doing what it’s designed to do. I understand that you don’t want the Traffic cop feature, but that doesn’t make it a bug. Since you want to disable the traffic cop feature, you add the code mentioned in the above reply, and linked again right here:
https://gist.github.com/joshfeck/1131145859a3fab58f4d
|
|
Omar Paloma
|
January 25, 2017 at 2:12 pm
Ahhh. Ok so I didn’t understand.
But I am now confused. If the traffic cop is enabled by default, how can a one user register one or more other users if all users have to be logged in to avoid the traffic cop (without the code added)?
What is the function of the “Force Login for registrations?” switch if it is not the Traffic Cop feature?
|
|
Josh
|
January 25, 2017 at 2:30 pm
Force Login for registrations makes it a requirement to be a member to register for an event. This is because you can’t log in without a membership, and if you can’t log in, you can register.
The Traffic cop is different because if you do not have a membership account, you can register without logging into the website. If you have a membership though, the traffic cop feature tells you to either log in to your membership account, or to use an email address that’s not associated with a membership account.
The traffic cop feature prevents the following scenario: A member of your site goes to your website and buys tickets at full (non-membership) price. Later, they realize they could have gotten their tickets at membership prices, but they forgot to log in to get their membership priced tickets.
|
|
Omar Paloma
|
January 28, 2017 at 3:33 pm
Thank you Josh,
This doesn’t Gist doesn’t work. I want to say again the the issue I have is with the additional attendees, not the primary attendee. I have seen other EE users also make the same clarification. Is this Gist meant to work for both the primary and the additional attendees?
|
|
Omar Paloma
|
January 28, 2017 at 4:09 pm
I carefully studied what the previous user did in the link from my post above and appear to have solved the problem. It was you, Josh, who also answered their post. Perhaps you can tell me how I can fix this so that a plug-in update won’t undo the fix?
|
|
Tony
|
January 30, 2017 at 9:15 am
The code Josh provided uses a filter that is wrapped around the whole section of code you are editing (as mentioned in the other thread) – http://take.ms/4FloZ
So if its not working then your custom filter may not be loading, or loading too late.
I just tested the filter Josh provided and it works fine for me, here is the default behavior – http://take.ms/yG8AT
Then I added Josh’s code to disable the check for all users:
add_filter( 'EED_WP_Users_SPCO__verify_user_access__perform_email_user_match_check', '__return_false' );
To my functions.php file and re-ran the same test – http://take.ms/rOTgt
Now I’m at the end of the registration asking for payment – http://take.ms/SrfRp
That seems to be exactly what you are looking for is it not?
If you are using the top function in the gist provided, that only works for logged out users, if you’re registering whilst logged in it continue to run as usual.
|
|
Omar Paloma
|
February 4, 2017 at 9:15 am
🙁 I am not a developer.
I just want my users to be able to register.
I want to be able to allow those who are logged in to have a discount.
I want them to be able to freely register other people whether or not they or the others are logged in OR have a valid user ID
What step or steps do I need to take to deliver this result.
Is there someone I can call at EE to discuss this?
|
|
Josh
|
February 6, 2017 at 10:54 am
Hi Omar,
This part:
I want them to be able to freely register other people whether or not they or the others are logged in OR have a valid user ID
requires some custom PHP programming. We’ve outlined the steps in this thread that can be taken by a PHP programmer to make that happen. You can contact a PHP developer and they can assist. We cannot troubleshoot and cannot change the code on your site over a telephone call.
|
|
Omar Paloma
|
February 6, 2017 at 11:13 am
Hey Josh,
I appreciate you taking the time to give a response. It isn’t helpful.
I wouldn’t expect you or anyone at EE4 to solve this matter over a phone call. My desire is to short-circuit the time it takes to solve a problem.
The process of getting a clear understanding of the software is difficult. There are features advertised that don’t work as expected and the documentation is poor. This is not to say that my understanding is correct I am simply saying things don’t always work according to how they appear and/or sound in your promotion. In this case, it doesn’t make any sense, to me, to allow a person to purchase multiple tickets obviously for others but then force the additional ticket holders to have to log in order to register. It also seems to be a snag if A purchaser wants to make subsequent purchases to the same event. The are, at least on my site, locked out.
Finally, while I have sufficient knowledge to follow your instructions but when sometimes it simply doesn’t work and, really, I don’t think I should have to alter the code for this kind of issue.
I have tried multiple ways of getting help from EE but some of your messages are come across as unhelpful to the point of being condescending or arrogant. It’s almost as if you are annoyed that there is a question.
If the software is only aimed at developers with PHP experience and/or it is obligatory to hire a developer to troubleshoot basic problems, that should be stated up front.
If not, the EE documentation should be updated to ensure that the use cases you highlight are clearly defined as to the implementation and scope. This will save you, as an organisation, a fortune in support calls to answer questions that are just not well explained. That money can be funnelled back into making a great product even better.
I don’t dislike EE. I am sure someone will respond challenging my comments here. But there are many similar questions in the forum so, clearly, this isn’t a edge case. There is room for improvement both in the product and the support.
If you wish to mark this comment private. I am happy for you to do that provided you are also happy to take this as positively directed feedback
|
|
Omar Paloma
|
February 6, 2017 at 11:28 am
BTW, I find guides, like the following from your blog, enormously helpful. Parts of this information should be in the original documentation.
Registration Statuses in Event Espresso
The Event Espresso sales funnel, or progression of registration is as follows:
Incomplete registration – When your audience selects at least one ticket and proceeds to the registration step. This is people who have started a registration or begun to purchase tickets but have not completed the registration form. You can find the number of incomplete registrations when you visit Event Espresso > Registrations and look at the Incomplete count at the top of the list table:
Event Espresso Incomplete Registrations
Pending Payment registration – When your audience submits the registration form AND your event requires payment. You can find the Pending Payment registrations when you visit Event Espresso > Registrations list table. Then filter the records by Pending Payment:
pending payment registrations
Approved registration – If payment is not required AND the Default Registration Status of your event is set to either Approved or Pending Payment, then after your audience submits the registration form, the registration is automatically converted to a Approved.
Not Approved registration – If the Default Registration Status of your event is set to Not Approved, then after your audience submits the registration form, the registration is automatically converted to Not Approved, at which point you can manually accept a registration. Once the registration status is set to “Pending Payment” the attendee can pay for their tickets.
You can also find all the registrations for an event from the event editor page itself. If you look at the Update Event box, you’ll see several quick links for registrations of each status with a valid registration.
|
|
Josh
|
February 6, 2017 at 11:42 am
Hi Omar,
Put simply, when you want them to be able to freely register other people whether or not they or the others are logged in OR have a valid user ID,
you are trying to use Event Espresso 4’s WP user integration add-on in a way that it wasn’t designed to be used. That’s why we don’t have documentation that covers your specific use case. A developer can help you extend Event Espresso’s WP user integration to make its feature set fit your exact specifications.
The feature set that comes out of the box is outlined on the product page:
https://eventespresso.com/product/eea-wp-user-integration/
|
|
Omar Paloma
|
February 6, 2017 at 11:52 am
Josh,
I have just re-read your documentation including the wiki. The implicit understanding, by offering a ticket that allows one person to register another, is that ONLY the primary registrant needs to be logged in. I am saying that we have run into an issue where the primary attendee IS logged in and can’t register other attendees.
We have also run into issues where the primary user IS NOT logged in and cannot register additional.
So it appears that this feature is only useful for one person registering him or herself while logged in.
Is that how they plug-in is meant to work?
|
|
Josh
|
February 7, 2017 at 7:47 pm
Not exactly, and this all goes back to the specific feature that’s conflicting with your goals it seems: the Traffic cop feature. The Traffic cop feature is intended to stop a member from registering without being logged in.
I explained this earlier in the topic, but for the sake of clarity, here’s a use case that helps explain why they built the traffic cop feature:
Let’s say you have a member price ticket, and a non-member price ticket. One of the members of your site goes to register and they’re not logged in, so the select the non-member ticket. The traffic cop feature will stop them from proceeding, and tell them to log in. This way they’ll get the member price ticket. Otherwise if it didn’t, they might later realize that they could have gotten the member price ticket, and that could turn into a situation where you now are dealing with partial refund requests.
That’s the idea behind the traffic cop feature. Not everyone seems to like the traffic cop feature, possibly because it’s not important that the members log in to get their member prices. So there’s a way it can be disabled. I gave you the link to the code example earlier, and since you’ve added the code to your site and the code isn’t doing what you want it to do, that could mean it’s not loading at all, or it could mean it is loading, but there’s still some expectations that are not being met.
I can help you make sure that the code is loading, for example are you adding the code to a site specific plugin, directly into a WordPress theme function file or elsewhere? We recommend adding the code to a site specific functions plugin.
Beyond adding the code to disable the traffic cop feature, if you have other requirements for the WP user integration, I can recommend contacting a PHP developer. A developer can put together some code to extend the basic functionality of the WP User Integration add-on, to your specification.
|
