loushou

Great. Thanks again guys for reporting this!

Loushou

Hey @bradleysp & @regenbauma, I just created another patch, 1.6.3. Seems to me that in both your cases, this may have something to do with the server setup, because it does seem to work in several environments I have tested it in. Despite that, I have made a few changes that could solve your problems. Let me know if this solves it on your setups. If not we may need to dig a little further to figure out the exact problem that is manifesting on your servers.

Thanks,
Loushou

Hey @bradleysp. I tracked down the hidden event problem and repaired it. I also added the ‘protected event’ functionality that you suggested. You can see both of these in the latest release of OpenTickets Community Edition, 1.6.0. Thanks for the great suggestion!

Loushou

Hey @regenbauma. The answer is tickets are currently meant to be simple products with no variations or attributes. This may change in a future version or extension, but as of now no attributes or variations will work on tickets.

We are currently working on a few extensions, one of which could solve your dilemma, which would allow multiple ticket types to be assigned to an Event Area; however, it is not yet complete. You can join the mailing list on the website to get updates about the new extensions as they come out.

Hope this helps,
Loushou

@bradleysp Sorry about this. I missed his email about it. Totally my fault. I will investigate further.

Loushou

Alrighty. I will speak with him about the hidden issue then. As for the ‘protected’ events feature, it is on the todo list. Sorry for the confusion.

Loushou

Hey @regenbauma. Glad to hear it is working for you now. As for the non-profits question, you should open a dialog with @quadshot by sending an email to him at [email protected] . He will provide you the details and ask the appropriate questions. Or you can visit the OpenTickets Website Contact Page and open a dialog that way. Either method will get you with the right person.

Loushou

Hey @bradleysp. We have tested the ‘hidden’ problem on a few different setups and even from fresh installs on those setups, and we cannot see to reproduce the 404. It would be great if we could find a way for us to reproduce the problem or if we can view the problem in action on your site, so that we can track it down and solve it if it is a code problem.

Loushou

Hey there @bradleysp. We have a fix for this in version 1.5.4. It turns out that on some server configurations dompdf (the PDF library we use) has problems rendering PNGs that have any transparency. Apparently this is a known issue. To solve this problem we have changed the format of both the barcode and the map to jpg and now it gets added to the pdf just fine.

Thanks for reporting this man,
Loushou

Hey @regenbauma. We were able to track this down. It was only affecting anonymous users, as you suspected, and a patch has been added for this in version 1.5.4. Basically, the process of setting the cart cookie was happening after output was sent to the user, so it was never getting set. It did not affect logged in users because of the awesome persistent cart feature of WooCoommerce.

Anyways check it out,
loushou

Yes. Seeing it not working would help greatly. At that point I would be able to debug more of the process and hopefully see exactly what is going wrong.

Loushou

Hey @regenbauma. After looking at your site, the problem is as follows.

Ticket products are not designed to be purchased via a ‘product’ page. The link you provided above is to the product page of the ticket product. This system was designed so that a given ‘ticket product’ can be reused for multiple different events, if needed. Think about a movie theater for instance. You might have a standard general admission ticket price of $8.00, but you may have 15 movies playing currently. Keeping a different ‘ticket product’ for each movie would be cumbersome, especially if there was a price change because of upper management. Allowing the re-use of one ‘ticket product’ that is $8.00 across all the movies, makes this more manageable.

Instead the tickets for an event should be purchased via the ‘event page’. In your case, you may have only a single event with a single showing. Your event might live at the url https://tix.serverspace.com/events/8th-day-havdalah-concert/2014-10-25_8-00pm/ . This page would describe your event (as you have done on the product page), and would have a nice interface for selecting the number of seats the user wants (something the software provides for you, which you can customize with css). Once a number of seats have been selected, the user can travel to the cart and proceed with checkout.

I would say that this is the source of your current problem for sure. The reason is because the software is designed to remove tickets from the cart that are not associated to an event, because otherwise the system does not know which event to deduct availability from, not to mention a plethora of other problems. By purchasing a ticket from ‘a product page’, the software has no idea what event the ticket is actually for, so it reacts accordingly. I recommend following the steps outlined on the OpenTickets Community Edition page, under the Creating your first Event, Start to Finish heading. This should get you on the right track.

Loushou

Hey there @bradley. This sounds like a new feature request. Currently you can do ‘hidden’ events, which are accessible to anyone but do not display anywhere, thus only people with the link will know how to get to it. You also currently have ‘private’, which only admin users can see. Protected sounds like a great idea for a new event status. I will add this to the feature list, and see if we can get this worked in.

Loushou

@bradleysp – have tested this on a few of my servers and it seems to happen on some but not on others. I am thinking this may be a server configuration issue, related to the dompdf library we use. Despite that, we should address it in the software, and at least try to provide a work around. I will do some more digging and see if I can figure something out for it. I will keep you posted.

@bradleysp, I tracked this down and created a patch. Now links clicked in email go through the proper process of authentication and no longer pop that error. Thanks for reporting it.

Loushou