|
Nick Putman
|
February 9, 2014 at 1:31 am
Hi,
I would like to add a couple of price points for an event that are hidden from the front end of my site, so that only the administrator can add people at these price points using the admin section. Is this possible with EE?
Thanks,
Nick
|
|
Nick Putman
|
February 9, 2014 at 11:58 pm
I can see that there isn’t actually a way of selecting a price point when adding an attendee in the admin area (it seems to just default to the first price point). Also there doesn’t appear to be a way of adding an attendee who has yet to pay – i.e. it’s only possible to add someone who has paid. I would like these two features added if possible.
I suppose the only way around this for now may be to hide a price point from everyone but logged in users on the front end. Would this be possible?
|
|
Tony
|
February 10, 2014 at 5:22 am
If your attendees currently do not log into the site before registering onto an event then you can set a ‘Members price’ for each ticket type. The admin could then register these user onto the event using those pricing options.
However this would be visible to anyone logged into the site, so if you have attendees who are members they would also see these prices.
EE4 improves upon the admin registrations but whether or not it is suitable currently depends on your feature set.
|
|
Nick Putman
|
February 10, 2014 at 3:06 pm
Thanks Tony – that is a useful workaround, as I am the only user on the site, but I would prefer one of the following two options:
1. Have all of the standard price points showing, and additional price points that are hidden using CSS or some other method from non logged-in users.
2. A way of adding a booking using the admin section, setting the price point manually, but marking the booking as unpaid.
Nick
|
|
Nick Putman
|
February 12, 2014 at 9:02 am
At the moment it seems that the best I can do is to book people on from the admin section, adding the price of the place, which is entered as the price they have paid, and then going into the MySQL table for attendees and manually changing the total_cost and amount_pd columns, as well as changing the payment_status column from ‘Completed’ to ‘Pending’, so that everything looks as it should when the attendee views their payment page. Clearly this is not an ideal method though.
|
|
Tony
|
February 12, 2014 at 1:33 pm
Hi Nick,
You do not need to alter the MySQL table.
If you manually add the attendee.
Leave the price blank (it will then default to 0.00).
Edit the Attendee. The ticket prices will look like this http://d.pr/i/ogBD
Add the Price per ticket and the Qty of tickets then update the price using the ‘Update Price’ button http://d.pr/i/6Ttn
You can also select the ticket type on the left then use the ‘Update Record’ button to save the ticket type (changing the dropdown and then using the ‘Update Price’ button will not save the ticket type)
Sidney also recently created another function to allow the admin to select the ticket type when creating the attendee, which has been posted here:
https://eventespresso.com/topic/manually-added-attendees-are-shown-as-admin-under-option-rather-than-by-ticket/#post-77897
Please take note of the comments within the code as you’ll need to add a function_exists wrapped around the original function within core currently.
Does that help?
I have added the 2 points noted previously to a feature request ticket for future consideration 🙂
|
|
Nick Putman
|
February 13, 2014 at 1:23 am
Thanks Tony. I did look into adding an attendee with a price of 0.00, and then making adjustments in the admin section, but then the registration email that is generated contains 0.00, which is far from ideal.
I will look into Sidney’s function to see if I can make use of this.
|
|
Tony
|
February 13, 2014 at 7:11 am
Hi Nick,
I did a little digging and if you do not mind the multi-step process I think I have a solution for you.
You can admin the attendee via the admin (forcing NO emails to be sent) then update the pricing etc to how you would like it, then ‘resend’ the confirmation email to the user from the attendee list.
This email would look just the same as if they had registered from the front end, showing the payment amount due that you set for the ticket price when editing the attendee.
Using the function Sidney provided reduces a step (selecting a ticket after adding the attendee) and also when doing the steps he provided should allow the modification to be update safe.
The downside is (apart from the multiple steps) is the admin does not receive a registration confirmation email using this method.
Have you setup the function Sidney provided?
|
