John Hawkins

I’ll create a ticket to add this to the ticketing.css file during the next update.

We have talked at length about moving the ability to collect registration information to the page prior to the ticket purchase. It’s something we are likely going to add to a future version.

Thanks for the feedback. Glad you like the plugin.

If you sell multiple types of tickets, on the attendee page it will group all attendees based on their ticket type. There is an export button at the end of each group that will let you export just that one group.

There isn’t an ‘export all’ because the field types won’t match up since each ticket type can (and most likely will) have collected different sets of data.

There appears to still be an issue with the ticket links if you are using the default permalink structure. We’ll look in to this shortly, but until then the work around would be to change your permalinks to use anything other than the default permalinks.

Would you mind emailing a ticket link to info [at] 9seeds [dot] com so I can have a look?

Can you tell me what version of WordPress and what version of the ticketing plugin you are running?

No sweat.

We’ll look in to the event name/description thing later today.

OK, I see where the confusion is…

The email address in the header on paypal’s page isn’t something we control. If you are sending the payments to a personal Paypal account, the email is displayed in the header as the recipient of the payment. If you are sending to a business account, it would instead show the business name. That’s just standard Paypal functionality.

Hope that clears it up.

-sigh- I can’t believe I missed this during testing.

Fixing PRONTO.

(Sorry, I thought I responded to this earlier.)

The ticket options data isn’t collected until after payment is made. On the purchase page the plugin will collect the name and email address of the purchaser. After completing the sale, a link to the ticket itself is presented and all the fields you’ve assigned will be present.

– sigh –

use this instead:

add_menu_page('Tickets', 'Tickets', 'activate_plugins', 'eventticketing', array("eventTicketingSystem", "ticketReporting"), WP_PLUGIN_URL . '/' . plugin_basename(dirname(__FILE__)) . '/images/calendar_full.png',29);

Turns out, using position 25 overwrites the comments list item. Oops. ??

hspense: I found the issue which turns out to be a bug in WordPress that I have reported here.

I have a workaround that we’ll implement in an updated release shortly. Until then, to fix the issue:

Open the file named ticketing.php, line 68 currently looks like this:

add_menu_page('Tickets', 'Tickets', 'activate_plugins', 'eventticketing', array("eventTicketingSystem", "ticketReporting"), WP_PLUGIN_URL . '/' . plugin_basename(dirname(__FILE__)) . '/images/calendar_full.png',30);

Change it to:

add_menu_page('Tickets', 'Tickets', 'activate_plugins', 'eventticketing', array("eventTicketingSystem", "ticketReporting"), WP_PLUGIN_URL . '/' . plugin_basename(dirname(__FILE__)) . '/images/calendar_full.png',25);

Cheers

OK, we’re still digging. I’m running a copy of Thesis 1.8 locally and can’t reproduce the error which is adding an extra layer of ‘fun’ to the process.

Have no fear, we’ll sort it out. Thanks for info.

If you wouldn’t mind, while the plugin is activated, try switching your theme to twentyten and then see if the “Tickets” menu item becomes available.

We seem to be having a weird collision with a couple themes that causing our menu item not to show. If switching the theme works for you, please let me know what theme you are using so we can test against it.

Thanks.

Thanks for the suggestions! We really do appreciate them!

I think I know how you could deal with the group pre-order thing with the current version. Create a package called pre-order, but set the availability dates in the past. Set the price for the package as 1% higher than you intend. Then, create a coupon for the package and make it a 1% discount code. Send that code to the folks you want to give the ability to pre-order. When they type in the code, that ticket type will be available to them. Maybe not as elegant as you were hoping, but will do the trick.

As for attaching tickets to seats, that is not even in our long term plans for the plugin. It gets far too specific. Each venue, heck, each event, would require making a map and then mapping seat numbers and tickets and, and, and… My head just exploded. ??

Thanks again for the comment and suggestions!