[Barry]

Thanks for contacting us — and I’m sorry to hear you’ve experienced problems.

I’d love to start by confirming a few things: you initially noted you had the same problem as described in this topic. However, that involves importing events from Google Calendar whereas it sounds like, in your case, the problem relates to recurring events and perhaps there is no connection with Google Calendar — is that correct?

I have all of the plugins updated, and gone through the disabling of everything else but ETC and get the same issue.

Thank you for doing this, your time spent trying this is appreciated.

Can you confirm, though, if after deactivating all other plugins and switching to a default WordPress theme, you created a new series of recurring events? If so, did the problem impact those newly created events also?

I felt it was important to confirm this because, in the past, users have hit up against this problem and found that deactivating their plugins etc makes no difference to the events that have already been created and impacted by this problem. However, it’s often the case that by this point the ‘damage’ has already been done to those events and so a better test is to create a fresh series.

Thanks – and let me know if you need me to elaborate further 🙂

[Barry]

Hi Dawn,

Thanks for contacting us — we take security very seriously and will of course investigate and report back to you 🙂

We did already receive a very similar report earlier today (though it seemed to be from a different person) by email and have already begun to work on this, so we should be able to update you before too long.

I would like to take a moment to note that email is indeed our preferred means of dealing with reports like this: as you can imagine, if a report containing valid methods of compromising a website are posted publicly the results may be less than satisfactory for a great many website operators. For that reason, I have redacted your post and removed any details from public view.

Thanks again for highlighting this and we’ll update you with our findings in due course.

[Barry]

Hi again Olivier,

It’s not necessarily a simple change to make, because we have existing code in place that uses different date formats according to whether a regular view or month view is in use — and some care would be needed to avoid collisions with that.

So long as you stick to the formats supported by the Bootstrap Datepicker component, though, you could override the defaults by utilizing the tribe_get_option filter hook:

function modify_date_picker_format( $value, $name ) {
    if ( 'datepickerFormat' !== $name ) {
        return $value;
    }

    return "YOUR_CUSTOM_FORMAT";
}

add_filter( 'tribe_get_option', 'modify_date_picker_format', 10, 2 );

The above outlines one possible strategy, but again this is an advanced customization and I’m afraid we have to leave you to largely chart your own route, here.

Good luck!

[Barry]

Hi Christopher,

I suspect this may relate to your theme’s CSS and so I would indeed need to be able to take a peek to assist further (you can share anything we need to do that via private reply).

Thanks!

[Barry]

Hi Olivier,

We have a Datepicker Date Format setting for just this reason!

You can find it within the Events → Settings → Display admin screen: however, it only supports numeric formats at this time so what you’re asking for isn’t possible at this time (unless you write custom code to accomplish it).

It could definitely make for a great feature request though — there may even be a suitable existing request you can up-vote — over on our UserVoice page.

Thanks!

[Barry]

Hi Sebastien,

Thanks for posting – and no, you don’t need to paste the full event address in the street name field 🙂

In this case you could try something along these lines:

[tribe_events_list address="yes" city="yes" country="yes" zip="yes"]

“Address” may not be the very clearest name for this attribute: our apologies if that caused some confusion. Also, a handy reference for this shortcode can be found here.

I hope that helps!

[Barry]

Hi Andy 🙂

We’d be stoked to help further if we can – particularly if there is a bug in the software. Can I ask that you login and post in the Event Tickets Plus forum, however?

Alternatively, if you have not yet purchased Event Tickets Plus and are using our core ticketing plugin – Event Tickets – I’d ask that you post across in our wordpress.org support forum.

Thanks!

[Barry]

Happy to help 🙂

[Barry]

My pleasure 🙂

I’ll go ahead and mark this topic as ‘pending fix’ (and have linked it to the relevant report on our internal bug tracker). As soon as the substantive fix goes out, we’ll do our best to post an update here.

Thanks again!

[Barry]

Hi John,

Thanks for contacting us and I’m sorry to hear you’ve experienced difficulties.

I strongly suspect the second point – the fact that stock levels are not decreasing – is a result of the first issue (the fact that something is going wrong during the payment process).

Although Event Tickets Plus can integrate with WooCommerce, it generally does not involve itself or interfere with the order process. So, if something is going wrong during the payment process, it’s highly likely that the problem sits at the WooCommerce level (or is an issue with the payment provider themselves, or the payment gateway plugin).

If you want to be doubly sure about this you could create a new product (ie, not a ticket but a regular product) and perform a test transaction. Note that for such a test the product would be ‘simple’ and of the virtual type – you’d also want to set the inventory. In essence, if you can replicate the same problem with the test product, then it is not actually a ticket-specific problem.

The next step from there would be to seek support from the Woo team, particularly if this is the gateway you are using (which I believe they support).

[Barry]

Hi Leonie,

Apologies for the further delay: some staff outages coupled with higher demand than normal for support has unfortunately slowed us down a little.

Can you help us with this then or should we contact Woocommerce?

Probably you should contact WooCommerce, however it may be worth performing a further test first of all if you have time:

• Create a regular WooCommerce product (not a ticket!) — set the product (which should be a “simple product” and marked as “virtual”) to use inventory and supply an initial stock level
• Make a test purchase
• Review if the behaviour of this product is in line with what you have experienced with tickets

If you see the same problem, then it is fundamentally a WooCommerce/payment gateway issue. There may in fact be valid reasons for it, but the WooCommerce team would be best placed to assist further.

[Barry]

My apologies for the delay in responding – some of the team have had a little time off and that combined with unusually heavy forum traffic has slowed us down a little.

It was working fine before for a long time and then stoped working. We never made any changes… How can you
explain that?

I can understand your confusion on this point.

However, to come back to what Andras already explained, the very same behaviour can be seen if you test this out using a regular WooCommerce product rather than a ticket. In other words, what you are experiencing is a facet of the ecommerce platform (WooCommerce) and payment provider (PayPal) you are using, rather than something specific to Event Tickets Plus.

If you’ve found that something has recently changed, then the likelihood is that the change was either within WooCommerce, PayPal or perhaps something in your site or PayPal settings.

I want to emphasize that we fully understand this could be a frustrating situation for you. Unfortunately, however, it’s not something that we are in control of (and I’m confident there are indeed good reasons for this, but the WooCommerce or PayPal teams would be better placed to field further questions on this).

[Barry]

Hi Jose,

That’s an interesting piece of work!

I do have to note however that the level of support we can offer for customizations – especially those of a highly specialized nature such as wrapping our plugin in an Android/iPhone app – tends to be pretty restricted. That said, I’d be happy to at least point you in the right direction if I can.

So I want to know which tables I have to modify to make a MySQL statement that allows the reservation of a ticket by a user from the app.

So I’m assuming you are using Event Tickets for reservations, here.

Like all our plugins, this currently stores almost everything in the standard post and post meta tables provided by WordPress. If you want to implement reservations via a set of raw SQL statements, you’d need to perform quite a few tasks including checks against the current ticket stock levels.

What I’d recommend instead of that is studying our existing code and in particular methods such as Tribe__Tickets__RSVP::generate_tickets() … while not designed for the sort of programmatic use you probably need here, it would be possible to write a wrapper around this and other existing code.

Wrapping our existing methods and functions would also potentially lower the risk of your app breaking if we change the way we store ticket and attendee data, whereas if you craft your own custom SQL queries you would be responsible for keeping them in sync with our codebase (unless, of course, you don’t update Event Tickets – which probably wouldn’t be a great strategy in the long run).

And i want to know too if there is another way to display the same calendar in the web and in the app (without touching MySQL tables).

You could cache the calendar views (or even cache the raw data) and serve up the cached content from within your app, but beyond that and without a more complete understanding of your architectural goals (and, as above, that would really be beyond the scope of support we can offer) I can’t think of a great way to achieve this.

If you need more in-depth support for this project, please do check out this list of developers who are independent of Modern Tribe and who may be able to facilitate some of your objectives.

Thanks for contacting us!

[Barry]

Hi Tristan,

Does the following snippet work for your purposes?

function remove_json_ld_from_month_view( $feed ) {
   return tribe_is_month() ? '' : $feed;
}

add_filter( 'tribe_json_ld_markup', 'remove_json_ld_from_month_view' );

You could add this to a custom plugin or even to your theme/child theme’s functions.php file, if you prefer—and please don’t hesitate to let me know if you need further assistance on that front.

[Barry]

This reply is private.

[Author]

Posts