[Barry]

Is there consistency (or lack of) between tickets on one hand and non-ticket products?

For instance if you create a test product with WooCommerce – that is nothing to do with WooCommerce Tickets (but of the same type, ie a “virtual” product) – can you replicate the same issue when using the gateway you mentioned?

[Barry]

That’s interesting. I believe I can see the same thing even on our demo site – so I’ll get this logged and hopefully we can get it addressed shortly.

Thanks for reporting this 🙂

[Barry]

Hi Charles,

That’s certainly looking quite specialized and so we may be very limited in terms of how much support we can offer here (it’s also hard to help without knowing what’s happening ‘under the hood’ with respect to your theme).

I’m also not entirely sure what you’re trying to achieve with your customizations to list.php – can you provide a few more specifics of what changes you are making there?

Thanks!

Barry

[Barry]

Hi!

Recurring events are not yet supported by WooCommerce Tickets.

If you do set up tickets for recurring events (and you can) they will apply to all events in the series – so one way of working around this would be to set up multiple tickets and set the start/end sale dates appropriately for each ticket (so that each one corresponds to a single recurring event instance). You would also have to take care of details such as the date/time printed on the tickets with some careful customization work.

That is of course just one way of working around this limitation – officially though there is no ‘native’ support of recurring events.

[Barry]

Hi John,

Definitely feel free to share your code with us (so I can see how your functions.php file looks when you’ve added that fix) – a service like Pastebin or Gist is an easy way to do this – as that will make it easier to see what’s happening.

[Barry]

Hi Josh, this is unfortunately a known bug and we’ll have it fixed in the next maintenance release. In the interim, can you try adding the following snippet to your theme’s functions.php file?

https://gist.github.com/jazbek/6169607

Note that normally you can omit the opening and closing lines that contain <?php and ?> … let me know if that helps!

[Barry]

Sure thing – it would be great to hear 🙂

[Barry]

Definitely – we’ve got this on the agenda and should be making some changes soon.

In the interim I’m afraid you would have to work around it by forcing the error reporting to a level that omits strict standards (as discussed above, that might be by setting a php_admin_value directive or else using ini_set() after WordPress has already set the level according to WP_DEBUG but before most other code runs – for instance by means of custom mu-plugins code).

Sorry for any inconvenience this causes in the interim.

[Barry]

Hi juliemoose,

There are already a lot of voices in this thread and I’d be worried that it could get confusing if we’re in the middle of helping you and someone from earlier in the thread – or someone new jumps in with their specific issue.

For that reason, can I ask you to create a new thread of your own for this (which is what we generally prefer in any case)?

Thanks!

[Barry]

Hi Daniella:

<?php echo the_time('l, ') ?><?php echo tribe_events_event_schedule_details(); ?>

So the first bit of code – the_time() – is a WordPress function that displays the time of the post (which isn’t the same thing as the time of the event – it really refers to the date and time that the event was created). The format you specified is just to display the day of the week – so yes unfortunately there is a good chance those will be out of synch in the majority of cases.

How about trying tribe_get_event_date() instead?

[Barry]

Hi Daniella,

Looks like your code was stripped from your reply (the forum doesn’t handle code very nicely) – could you add it a second time by sharing it via Pastebin, Gist or a similar service?

Thanks – and sorry for the inconvenience.

[Barry]

Hopefully they’ll be able to get you sorted here. We do plan on building a set of tutorials or other resources to improve the situation with regards to Headway integration – as we appreciate it is a popular theme framework – so hopefully the situation will indeed improve going forward.

Thanks for your continued support 🙂

[Barry]

Great stuff, hope all else goes smoothly with the project – but of course please don’t hesitate to create new threads if you need further assistance.

[Barry]

Hi Andrew: we’ve logged the filepath issue for Windows/IIS servers and the devs will address that as quickly as possible. For any other issues please create a new thread – thanks!

[Barry]

That’s possible (that it doesn’t work on the latest version of WooCommerce).

The thing is that from our perspective we don’t want to change the fundamental operation of WooCommerce itself – which others may not find desirable – and we can’t realistically support WooCommerce itself in addition to our own plugin beyond some very simple pointers in the right direction.

Though you may not be able to access support directly from WooThemes if you are not a paying customer perhaps you could seek help/find existing answers on their community forum which is free for all to access?

[Author]

Posts