[Barry]

Hi Chris,

Thanks for posting!

The calendar should respect your WordPress settings, so all you really need to do is tweak the Week Starts On option found in your general settings screen.

Does that help?

[Barry]

Hi Jeffrey,

Thanks for considering our plugins 🙂

Yes, Filter Bar is extensible and you can define completely new filters for it if you like. I’d add a caveat, though, that even for active license holders we cannot offer a large amount of support for custom development tasks (such as defining new filters).

That to say, what you want is absolutely possible – but would require some custom dev know-how.

Thanks!

[Barry]

Great, glad you were able to tweak things 🙂

I’ll go ahead and close this topic – but should anything else crop up please don’t hesitate to post a new thread.

Thanks again!

[Barry]

Hi Dawn,

Thanks for the extra info!

Unfortunately, though, I don’t have anything helpful to report. I don’t see the problem and so roped in some other team members who also attempted to replicate (and we did indeed test with real – as opposed to a simulated – iPhone) … again, we couldn’t see the problem.

Have you heard from other users that they are also experiencing this? I’m afraid on our end we either cannot see the issue or are misunderstanding your description.

[Barry]

Hi Shea,

The first thing I need to highlight here is that the level of support we can provide for custom dev tasks if really pretty limited. That said, I’ll try to steer you in the right direction if I can.

With regards to the code you shared in your gist, you are grabbing an array of event posts via tribe_get_events() and then loop through them. Within that loop you then call tribe_get_event_link() but are not passing the ID of the event.

Though that would still work in a “real” WordPress loop, in this case – despite the fact that you are calling setup_postdata() – the global post object is untouched by this:

setup_postdata() does not assign the global $post variable so it’s important that you do this yourself. Failure to do so will cause problems with any hooks that use any of the above globals in conjunction with the $post global, as they will refer to separate entities.

So, either ensuring the global post object is setup correctly or just explicitly passing the event ID ought to work 🙂

strtotime() expects parameter 1 to be string, object given in /…/plugins/the-events-calendar/src/Tribe/Query.php on line 220

I’m guessing the PHP warning above is the other problem you were referring to.

My guess is that this stems from the start_date argument you are passing to tribe_get_events(): instead of passing a DateTime object, I’d recommend passing a date string such as “2016-12-31 12:00:00” instead.

That leaves us with the JS error which seems to be coming from our This Week widget. I see it on your homepage, but can you confirm A) if the section entitled Coming Events is generated by that widget B) if it has itself been customized and C) if you are embedding it as a normal widget or via a shortcode?

Thanks!

[Barry]

…One other thing, is that we have found its not uncommon for users to miss the advice given in our knowledgebase and the Events → Settings → Add-on APIs screen itself with regards to the Auth URL – so it could be well worth revisiting this part of the process 🙂

[Barry]

Definitely, that does seem to point squarely at the source of the problem, though at the same time it’s clear we could improve our built-in error messaging.

Let me know what you find!

[Barry]

Hi Andy,

Sorry for any confusion – I was incorrectly jumping to a conclusion there 🙂

If you don’t have any caching mechanisms in place (and assuming you’re not on a managed hosting platform that provides this “transparently”) then I may have been incorrect.

With all that said, what query exactly did you run to remove the expired events? It sounds as if the query I provided didn’t work as expected for you and that you may have amended it?

Additionally, have you tried adding a new event (and subsequently trashing/deleting it) – and does that influence the total post count you see in the edit events screen?

Thanks!

[Barry]

Thanks for sharing the system info.

One of your plugins, WP SpamShield, seems to be the source of the error message. You could confirm this by disabling it – temporarily – and attempting to RSVP as an unauthenticated user.

Other than that, it may be worth connecting with the authors of that plugin (if you still require it) to see if there are any means of resolving this 🙂

[Barry]

Hi Ian,

So in two of your templates (but for the problem at hand, widgets/modules/single-event.php is the one that matters) you do something along these lines:

$excerp = tribe_events_get_the_excerpt();
$printexcerp = substr ( $excerp , 0 , 75 );
echo $printexcerp;

The problem is that slicing the string to precisely 75 characters can break a number of things.

It can, for instance, slice an HTML entity in half. It could also slice opening or closing HTML tags in half – and that is what seems to be behind the problem here (if you inspect the HTML source of one of the pages with this widget you’ll probably be able to identify exactly what I mean).

To cut a long story short, I’d strongly recommend revising that section of code 🙂

[Barry]

Thanks Kirk.

What I’d like to do is have you temporarily install and activate this plugin. With that done, if you can once again try to set up some tickets, we should get additional information (as an error message, at the top of the screen).

This might provide some insights as to what exactly is going wrong in your case. Please copy and paste or screenshot the error message and we can take a look 🙂

[Barry]

Hi Paul,

Thanks for considering The Events Calendar and our other plugins 🙂

1) Yes, a combination of the following plugins ought to fit your needs (re selling tickets to events):

• The Events Calendar
• Event Tickets
• Event Tickets Plus
• WooCommerce

2) You can indeed disconnect licenses from one domain then plug them into another. Generally speaking, though, there’s no need to activate your license for test/dev sites.

3) Single site licenses currently do work within multisite networks.

We encourage the use of a multisite licenses, particularly where lots of the sites on the network make use of our plugins, but this isn’t strictly required and if you’re only going to be using the plugin on one of those sites, a single site license is just fine!

4) Yes – the whole checkout process is in the hands of WooCommerce and at the stage we don’t interfere whatsoever.

That means you are free to use whichever payment gateway(s) you prefer. The setup in our video just happened to be configured to use check payments.

5) Precise positioning (of map pins) is indeed possible, but requires Events Calendar PRO.

I hope that helps!

[Barry]

Hi!

I’m sorry to hear you’ve been experiencing difficulties.

Looking at the initial block of errors you shared, the problem doesn’t seem to be restricted to queries generated by our own plugins – so it’s possible there are more general issues that need to be solved.

Caching is one of the best ways to improve performance and there are lots of different forms and places that caching can be applied, ranging from the month view caching option we provide in the Events → Settings → Display admin screen through to page, object and query caching.

Exploring those would definitely be worthwhile.

Do you recommend another way to add the custom fields and taxonomies?

What you are doing looks fine, but really custom development isn’t something we can provide a large amount of support for here in the forums.

[Barry]

Hi Ari,

I’m sorry to hear you’ve hit up against some difficulties.

I visited the domain/URL you provided when you opened this topic but couldn’t see the problem – month view and search seem to work just fine and I do not see the type errors you noted.

I do on the other hand see some 404s but they relate to assets from your theme and wouldn’t really impact on this.

Have you solved the problem? Was I looking at the wrong domain? Which browser/OS are you seeing this issue with?

Thanks!

[Barry]

Awesome!

[Author]

Posts