|
Brian
|
December 9, 2014 at 6:27 pm
I just upgraded to EE4 4.4.6p. The privately published event that I was working on no longer shows the ticket selector when I view the event so I can’t test the registration process. Other than publishing publicly, is there anything I can do to get the ticket selector to appear?
Thanks for your help.
|
|
Dean
|
December 10, 2014 at 1:17 am
Hi Brian,
Thanks for letting us know about this. I can’t see a workaround at the moment, but I will raise the issue with the developers to look into a fix for a future version.
|
|
Brian
|
December 10, 2014 at 4:08 am
Thanks Dean. Public Draft doesn’t show the ticket selector either. The only way I can keep going is to download the system to my workstation and create events publicly to test, and then hope I get production set up the same way.
|
|
Dean
|
December 10, 2014 at 4:35 am
Thanks Brian, I updated the ticket with that information too.
|
|
Brian
|
December 10, 2014 at 10:34 am
As a workaround I have patched EED_Ticket_Selector.module.php at line 146 to remove the the following OR clause that was added in the latest release so I can keep going:
|| (
self::$_event->get_active_status() != EE_Datetime::active
&& self::$_event->get_active_status() != EE_Datetime::upcoming
)
|
|
Tony
|
December 10, 2014 at 10:38 am
Thanks for keeping us updated Brian.
Just to note that code was added to remove the ticket selector for events that are
not Upcoming or Active.
This was to prevent events with a status of Cancelled or Postponed from displaying the ticket selector, however as you have noted this has also removed it from Private and Draft events.
This has been noted on the ticket Dean created for some developer feedback.
|
|
Brent Christensen
|
December 11, 2014 at 10:59 am
Hi Brian,
I’m Event Espresso’s lead developer.
I can not reproduce this issue that you are experiencing, here is a test post I created on a testing server that you can look at:
http://ee4m.eventespresso.com/events/the-password-is-123456/
Now the reason the Ticket Selector appears when you remove:
|| (
self::$_event->get_active_status() != EE_Datetime::active
&& self::$_event->get_active_status() != EE_Datetime::upcoming
)
from the Ticket Selector code is because your event’s status is either NOT Active or Upcoming. The datetimes for your event are most likely off, and that is what is preventing the Ticket Selector from appearing and NOT the fact that it is password protected.
The line of code above those conditionals:
|| post_password_required( $event_post )
is what hides the Ticket Selector if the post password has not been entered correctly. Had you removed that to get your event working properly, then it would have been an issue with the password protection.
So please reinstate the Ticket Selector code that you removed, then check that your event’s status is either Active or Upcoming (see: http://nimb.ws/sYl0mQ)
and adjust your datetimes accordingly until the status is correct.
Please let us know if that fixes the issue. If it does not, then Dean or Tony may have to request that you send login credentials for your site via a secure form, in order for them to investigate further.
Thank You
|
|
Brian
|
December 12, 2014 at 6:14 am
Thanks Brent. The event is inactive since it is privately published. I have to do that to test the registration process from end to end and get approvals before the event is made public. I could test like this prior to 4.4.6p. The new conditions prevent the ticket selector from appearing for privately published events. It also prevents the ticket selector from appearing for draft events since they too are inactive.
Is there a way to run through a complete registration as a test without making the event visible to the world?
|
|
Lorenzo Orlando Caum
|
December 12, 2014 at 12:19 pm
Hi Brian,
If you are using this approach for testing the event, then you could save it as a “draft.” That would make it available to admin-users on your site.
Then once it has been approved, then you could publish it.
—
Lorenzo
|
|
Brian
|
December 14, 2014 at 5:06 pm
Thanks Lorenzo, but drafts are also inactive so the ticket selector will not appear.
|
|
Dean
|
December 15, 2014 at 2:07 am
Thanks Brian,
I have already updated the ticket to mention the draft aspect as well. I’m hoping the developer will get a chance to look at this again shortly.
|
|
Josh
|
January 27, 2015 at 2:56 pm
Hi there,
This is fixed in Event Espresso 4.4.9.p, available now.
|
|
Brian
|
January 28, 2015 at 1:39 pm
Thanks Josh.
|
