Support

December 16, 2015 at 5:47 pm

Is there a way to get all registrants for an event to become users in WP, or enrolled in the classes?

Would all those registrants be included in our batch message send, or Contact list, or would the message only be sent to the one person who bought multiple tickets?

Is there a way to accomplish this?

Is this on any planned releases of the plugin?

December 21, 2015 at 9:32 pm

Yes. You can make this happen by setting the ticket limit per order to 1.

Yes, but then can we still register multiple people per order, if the ticket limit is 1?

We want to be able to register multiple people per order, have all of those people become WP Users, and thus all enrolled individually into LearnDash courses, with their own logins.

December 22, 2015 at 4:18 pm

Thanks Josh, Lorenzo actually already told me this earlier in the thread.

there is one outstanding question:

Is this on any planned releases of the plugin?

December 24, 2015 at 7:17 pm

Hi Josh,

The thing that I don’t get is that in these support threads what I’m hearing from you guys is that you don’t know how to make a decision about something, so you’re just not making it. I don’t think these are insurmountable issues that can’t be solved, or at least given to the control and choice of a user.

There are also other systems out there that can handle these questions fine.

So for example:

What if the person doing the registration is logged in? Do new user accounts still get created for any additional registrations?

Yes, why would this not be the case? We are trying to make new users on a single order with bulk registrations for an event.

What happens if there is already a user account matching the email address for one of the registrations? How should this be handled?

A popup that says “this email already exists, do you want to add this registration to that account? If not, please use another email” Then user selects yes or no. Simple.

Related to the above, validation will have to be done on the provided info for each registration as related to WordPress user accounts (and appropriate error response handling if it doesn’t validate)?

Yes, why is that a setback? Why can’t they just get an email that says “you have an account on this website now, because so-and-so registered you for an event.” Why would this be a prevention to moving forward with a desired user feature?

What happens if the registration form is setup to allow the copying of info to multiple registrations?

Then it copies. Is that problematic? If it can’t create new user accounts with duplicate data (username and email), then a pop up says “sorry, you can’t proceed without unique usernames and emails. These already exist.”

I know I may be giving you answers that you feel are over simplified, but this just doesn’t seem like a reason to not move forward on something, only because you can’t make a decision about what will happen. And I’m getting this answer on other posts as well. I don’t think it’s right to say “we don’t know what to do, so we’re not going to do anything, go pay someone to do it.” I do feel you should be more proactive as a company in responding to user requests like this. It’s not like we’re asking you to put time, money and resources into creating a brand new integration just for us. These are things that have applicable use cases for your already-advertised features.

I understand people can pay developers to customize this plugin to their needs, but what we’re bringing up here is not really so specific that it wouldn’t be applicable or useful to others. If someone buys the WP User Integration, which is a hefty price for what it does, by the way, that person would then expect that users will be integrated with registrations. This is why they buy it. This is why we bought it. So it’s not unreasonable to expect these controls to be in place, with simple solutions as outlined above.

The problem with an organization like ours to pay a developer to customize this is, what happens when there are updates? We pay again, and again for this feature? Just to be able to use two features that are advertised, that we paid for, but that won’t ‘link’ together? We are a non-profit run by volunteers. We chose your plugin above others because it met our needs the most with LearnDash and PaidMemberships Pro integrations (using WP Users Integration). So we are happy about that. But this is unexpected.

We don’t mean to be difficult with you, but as you can tell, this is a frustration that we are facing a dead end here with this.

January 8, 2016 at 1:11 am

Hello Josh, first of all thank you very much for your effort put into this. It is not unnoticed and we super appreciate your kindness in helping us.

However, I tested your plugin but it was not successful:

It did not create a user for the second attendee (I tried to buy 2 tickets)

It did not notify or stop me from using an existing email for the original registrant (perhaps that was intended though)

I also got an endless ‘spinning’ of the gear icon that just wouldn’t stop until I hit refresh. Hitting refresh on my browser took me to the page to finalize payment by clicking to go to paypal. But it loads and takes me to the footer directly, where I have to scroll up to click the button to finalize registration.

I’m not sure if that’s related. I’ll start another thread if need be about the endless spinning.

Payment works and the invoice shows the two registrants.

Thanks

January 8, 2016 at 1:25 am

More info:

I did get this message with another endless spinning gear icon, which continues to spin even after refreshing the page to view that payment had been “approved” (because I did it manually):

https://cloudup.com/cBU9tF59Bua

January 8, 2016 at 2:02 am

Ugh, ok, sorry Josh, but this time I think I found a real bug, and I tested first before writing this out.

Hi there,
I’m testing manual registrations on EE4 Version 4.8.29.p

When your sample plugin is activated:

The strange thing is that when I enter a registrant’s first name and last name, it is updating the first name and last name of the admin account that is used to make the manual registration.

This is not right since admin should have their own first name and last name, especially if it is going to appear throughout the site on published posts.

I tried this twice, and both times it just changes the name of the administrator account that created the manual registration.

Do you know of a fix for this?

For others reading this we also have:

WP User Integration Version 2.0.8.p

WP Version 4.4.1–en_CA

EE User extension made by Josh on Github here

Deactivating the EE user extension made by Josh removes this issue.

Thanks!

January 12, 2016 at 10:09 am

Then for this one:
I also discovered this plugin add-on won’t work if a registration is manually approved. Meaning, a user account won’t be created if a registration needs to be manually approved.
This is problematic because we are getting the “Pending Payment” again after returning from a Paypal purchase.

Josh’s reply: Can you check to see what you have set for Default Registration Status in the event editor? Generally that should be set to pending payment.

I haven’t been changing these – they are set to “Pending Payment.”

But I don’t want to set it to “approved” in case their payment doesn’t go through because of any potential IPN issues or declined credit card, or what not.

Is that what you’re suggesting?

January 13, 2016 at 8:08 am

Hello Josh,

For this one:

original: This is definitely happening only when the “enhanced users” plugin is activated. I just tested it again. Here is a screenshot of what I entered as an Admin: https://cloudup.com/ckb0QZv4ZOh And then it for sure did this to my Admin user’s name: https://cloudup.com/caA30nIQ-js

JOSH’S REPLY: I’m not seeing this happen on my test sites. We may not be on the same page here though. So I will ask some questions and your answers are important:

1) Are these registrations being made on the front end of the site? Yes or No.

No.

If Yes, then you really should not be logged in if you also want a new user account created. It seems to work that way anyway with the extension plugin, but it’s really not intended because the form autofills the existing user’s information. If No, then you’re adding the registrations from the back end, which shouldn’t create or update user accounts.

It is updating user accounts when manually registering them in the back end.

2) Can you try the test with only these 3 plugins activated? Event Espresso core, WP Users, and the extension add-on that I built for you?

Yes, I had only these activated: https://cloudup.com/cfyLCnjjTdS

I used this info to add a registrant to an event in the back end: https://cloudup.com/cC95o0Z_P-O

And it turned my Admin account name to this: https://cloudup.com/cXVYUGnLeiW