[Barry]

Any event you set up will still exist upon removal of the PRO plugin … however, if you use PRO features such as setting up recurring event patterns then you’d see effects such as the first event in the series staying in place and the future instances effectively disappearing (though the data would still be in the database).

Does that help at all? If you need me to clarify anything in further detail please don’t hesitate to ask.

[Barry]

Can you provide the username/password necessary to see your site (please email me privately at [email protected] and include a link to this thread) and also provide the URLs to specific events where you’ve set up tickets?

If so that would be great.

[Barry]

Hi Christopher – let me address your main points in turn.

Honestly guys I appreciate everything you have put in to this plugin, and the bug fixes with the latest WooTickets released on March 5th, but wouldn’t you consider the option to delete people from the attendees list as a base/standard feature?

So what we’re planning (for a future version) is to remove attendees associated with a specific order when that order is deleted; as I understand it we won’t be allowing the direct deletion of attendees from the attendee list, though.

As you are aware this didn’t make the cut for our 1.0.1 release however that was primarily aimed at fixing bugs and ensuring compatibility with the latest version of WooCommerce; we should see a more feature-driven release next.

To the problem at hand:

The “Organizers” of this event will rely on that portion to check people in and out. Given they can still do their job, its going to be horribly confusing when I have done over 50 tests, and have over 50 entries in there that were just for testing purposes

OK, so if you are at all unsure about working within the database then you may prefer to simply duplicate the event (especially since it is just one event, if I’m understanding you correctly) and leave behind the test orders.

However, if you prefer to remove attendees directly and feel confident in terms of working with the database then you will wish to seek out entries in the posts table with a post type of tribe_wootickets … corresponding entries will exist within the posts meta table and you will probably wish to clear those out, too.

For the benefit of any other users reading this, if you need to test things out it’s generally better to set up a separate testing environment – but if that isn’t possible or practical then setting up a test event (rather than working with the ‘actual’ event post) would allow you to cleanly delete that event plus any associated attendee data before going live.

If you still have one, wouldn’t mind using one to try out the “Pro” version of events manager.

Feel free to email Leah ([email protected], please include a link to this thread) and she may be able to help here – I don’t think we can give you another plugin for free here but we can probably provide a small discount 🙂

[Barry]

Hi Joe, guessing from the comments here that you figured things out – the only thing I would add is that changes to core code will be wiped when a plugin update occurs.

In any case it sounds like you’re all sorted here so I’ll go ahead and close this thread 🙂

[Barry]

My understanding is that you should be ok so long as you go through 1.3.3. I’ll look out for your email and reply with a link to 1.3.3.

[Barry]

Hi Berrie,

We can definitely put the suggestion forward for the team to consider.

Regarding the original problem, again I looked at the calendar and past events (from March 4 for instance) are still present – is it looking like this issue is resolved/is there any further information you can provide?

[Barry]

Hi Samantha, sorry to hear that you are experiencing problems here. Based on feedback from users experiencing this issue it’s looking like it has been resolved as of version 3.0 of our plugin – which will be the next major release.

For the time being what I’d recommend is disabling the display of errors (see my earlier comments in this thread) – that’s a best practice in any case for live websites and may effectively resolve this for you.

[Barry]

Great, glad it’s solved.

If I’m understanding you correctly the email structure is a facet of WooCommerce rather than WooTickets – could be you’ll find some resources to help you customize that over on the WooCommerce codex/support pages.

Since the original problem has been resolved however I will now close this thread. Thanks!

[Barry]

Hi Schalk,

I’d love to be able to give you more to work on here but I’m afraid I can’t. Decisions as to what new features will and won’t “make the cut” are still being made and the team’s primary focus, for the time being, remains on the development and release of The Events Calendar 3.0.

So, regrettably, I can’t yet indicate if this feature will be taken up.

I would however love to visit Cape Town – I suspect the water is a degree or two warmer than it is here in the west of Canada 🙂

[Barry]

Not running any Jigoshop on that site at all.

Yep, sorry – you’re absolutely right, I see now there are basically two different sites (I had followed the Store link in your menu which led me to the other site and what looked like a Jigoshop installation). Sorry for the confusion!

And I have set up other products and none work.

OK, in that case unless you find that other products do work with WooTickets deactivated – and please do let me know if that is the case – then this is probably an issue with WooCommerce/a WooCommerce add-on and if so you would need to reach out to their support team.

[Barry]

Hi Amilkar. I’m going to move this across to the Eventbrite Tickets forum.

Just to confirm, did you see this error when you tried to update an event you had previously imported from Eventbrite, or was it when you tried to update an event which had been created within WordPress/The Events Calendar and that you were trying to “push” to Eventbrite?

[Barry]

Hi Thomas,

That doesn’t sound too great. It’s sounding to me like a problem with WooCommerce or one of your WooCommerce add-ons rather than with WooTickets.

I tried to assess this by running through the checkout procedure A) after selecting a training course and B) for a regular non-WooTickets related product … however I then noticed that you seem simultaneously to be running WooCommerce and Jigoshop.

Though I don’t know this definitively, my instinct is that that has potential to create some conflicts. It also meant I couldn’t really test if this is isolated to WooTickets-products … are you able to set up some other products with WooCommerce and test if you can buy them without seeing any errors?

Cheers,

Barry

[Barry]

OK, well that’s definitely worth trying. If you don’t want to do this because it might disrupt your live site then consider using a staging or testing site.

This should be as close to a duplicate of the live site as possible (though not ideal, you could even install a new copy of WordPress in a sub-directory of your existing hosting account and turn that into a duplicate site): see if you can replicate the problem there, then run through our troubleshooting steps.

Alternatively, if you don’t want to do that, the best I can suggest is recreating your events since based on what you are telling us that would also seem to resolve this.

[Barry]

Interesting.

If I look at your calendar for this month I can still see events from 4 March through to 8 March … are you finding that events are purged when the month changes, or after a period of n days?

[Barry]

I’ve no idea why we can’t see the event title. Can you send your theme across as a .zip so I can test it? (Please send to [email protected], marking for my attention and including a link back to this thread.)

[Author]

Posts