[Brook]

Since this topic has been inactive for a spell we are going to archive it. Please note, if you need anything else or something is not yet resolved please open a new topic. We would love to help!

Cheers!

– Brook

[Brook]

Thank you for marking the thread answered!

– Brook

[Brook]

Hey Jo,

I have tried to reproduce this a few different ways. No success yet. I am going to try a couple more tomorrow, and I will let you know the result.

Cheers!
– Brook

[Brook]

Howdy again Northwest,

I have some good news on the Eventbrite API front, we just released version 3.10.1 of Eventbrite Tickets. You can update from your websites WP Admin area. This release is intended to fix the new issues that started hitting your site this week.

You might still see a deprecation notice in the tickets area. Fortunately the notice is not describing a real problem on your site. Our 3.11 release of Eventbrite Tickets will remove that notice completely, but in the mean time you can hide that notice by disabling WP_DEBUG on your website if you’re so inclined. More information here.

If you continue noticing any glitches with Eventbrite Tickets please let us know. Especially the one that caused you to open this topic. You should now see your events from WordPress pushed to Eventbrite along with their tickets. Cheers!

– Brook

[Brook]

Thank you very much Jo for giving that another whirl. I know it’s not an easy test to run.

I would like to try to reproduce this issue on a test site. Before doing that I need to collect a little more information from you. I appreciate you already shared your system information when you opened the topic, but it looks like the bottom half of it is missing. Would you mind grabbing your system information again and pasting it here? Make sure to use the ‘Set as private reply’ checkbox to protect your private information from the public. You can find the system info by going to WP Admin > Events > Settings, clicking on the “Help” tab, and scrolling down to the ‘System Information’ box. (Or by going to [yoursite]/wp-admin/edit.php?post_type=tribe_events&page=tribe-events-calendar&tab=help)

A few other questions for you that will help me pursue a couple of theories:

1. What timezone are you using for your site? This can be found in WP-Admin > Settings > General.
2. Who is your website host? Do you know what country your server is located in?
3. Do you do daylight savings from March – November?

Thanks!

– Brook

[Brook]

Howdy Nick,

I would love to help you with that. That’s a pretty in-depth thing to do, but you are already well on your way.

The standard WP_Query does not have enough capability built-in to do this. However, it makes it easy to add capability to it. Checkout the posts_where filter. Using this filter you could add a custom parameter to WP_Query ( which will also automatically be added to tribe_get_events() since that function is a wrapper for WP_Query ). Let’s say this new Query parameter is called “tribe_dayofweek”. I recommend you checkout our own extension to posts_where, which can be found in:/the-events-calendar/src/Tribe/Query.php:514 Right there on line 522 you can see how we detect if someone has declared the additional Tribe parameter ‘start_date’, and as you read on you can see how we modify the where clause of this SQL query.

In this case you are going to want to add a where parameter which implements SQL’s DAYOFWEEK function. If you’re like me the MySQL documentation is not always very helpful. But here’s a pretty comprehensive answer on stackoverflow on how to implement this function. It’s the same SQL function we use for our Filter Bar (which allows users to select which day(s) of the week they would like to see events for) and the same SQL WordPress uses for its date_query =>dayofweek magic.

There you go! Let me know if you have any questions. Thanks for posting, Nick.

– Brook

[Brook]

Sadly, it makes sense that your backup does not work either. Eventbrite has discontinued the API that your backup relied on, there is no way to get it working again without Eventbrite themselves restoring the old API’s functionality — something there are not likely to do. They do offer a provision to extend the old API’s functionality, but I believe you had to request that before it was discontinued.

I really wish we could do a full release in the next hour. But that’s not humanly possible, at all. We have an Eventbrite Tickets 3.10.1 release candidate out, which can be downloaded here. However, it has not undergone QA and it has known bugs. We of course do not recommend running it on a live site unless you have good backups you can revert to should the worst happen. According to current reports this release candidate has fewer issues then 3.10 now that Eventbrite has discontinued the API which 3.10 and under used. However, without thorough QA there is no way to know if some users might have bigger issues with this release candidate.

A thorough QA of this Release Candidate might take a few weeks, unfortunately. We often spend hundreds of man hours developing and QA’ing every release, and this one is nowhere near that yet.

I am truly sorry northwest. We are in a pickle since the API update. We are doing our very best to push a fix out the door, but that takes time.

Please let me know if you have any questions.

– Brook

[Brook]

Howdy Jo,

I would love to help you with that. You have a very keen eye to notice that one year in advance!

I am sorry to see you are having issues. I suspect that a conflict is happening. Divi themes and The Events Calendar have not always worked well when run together on the same site. We are actually looking into seeing if there is anything our plugin or Divi could do differently so that they will work great together. But, in the mean time conflicts will continue.

In order to proceed we will need to test if a “conflict” is happening. This guide walks you through how to test for a conflict, and then identify what is conflicting. Once you make it through the first heading, where you have switched themes and disabled plugins, try editing one of the recurring events that is not appearing in July 2016. So go to your WordPress admin > Events > Edit Events, find one of those events, and click Edit All. Make a minor temporary change to the event, maybe add the word “test” to the end of the event description. Save and update the event. You will see a progress bar at the top as it saves your changes. Once it’s finished you can leave the Edit event page and once again view July 2016. Does that event appear now? If so, a conflict is indeed happening. One of your plugins, or your theme, is stopping The Events Calendar from saving all occurrences of certain events.

Let me know the result of that diagnostic test, and we can figure out hot to proceed. Or if you have any questions or anything, I would love to help with those.

Cheers!

– Brook

[Brook]

Thank you for sharing the error message. That helped determine the issue. We started seeing that bug last week as well, and have added a fix for it in our next release (version 3.11) which is due out in a few weeks. It is also possible that a fix will be available in our maintenance release, 3.10.1. Which will come out sooner.

Eventbrite has updated their API this week and there are quite a few errors happening right now. You might have seen this sticky post in this forum. Keep an eye out for the the 3.10.1 update. Until, unfortunately the Eventbrite API has broken compatibility with our current 3.10 plugin, and so things will not be working great. I wish I had better news on this front.

– Brook

[Brook]

Howdy B,

I would love to help you with that. There would be two ways to get this feature in your calendar. Josh already did an excellent job of outlining the first method, but unfortunately it will require some PHP knowhow.  He clearly simplifiedas best as he could, but even still when modifying your PHP site you need to know a little PHP. If that does not describe you or someone in your employ, then this method won’t work.

The second and final option would be to officially suggest this as a feature on our feature suggestion page. But, the reason Josh did not first mention this route is because it takes a while for a feature suggestion to get implemented, if it does at all. You will have to wait an see how popular this idea is. If it is popular then we would certainly be keen to integrate it. Usually we implement the most popular ideas first.

Does that all make sense? Will that work for you? Please let us know.

Cheers!

– Brook

[Brook]

Howdy Pedro,

If you go here you will see that our Spanish translation is no longer complete. Recent updates to the plugin changes the wording, but no one has volunteered to translate. If you are interested in volunteering to translate it, then read this guide which details what’s involved. We would happily give you a free license or renewal if you update the translation for Core and Pro.

 

 

Since the original poster has not responded in a few weeks I am going to archive this topic as per our forum rules. Benjamin or Pedro, if either of you need anything please feel free to open a new topic dedicated yo your problem. We would love to help! Cheers!

– Brook

[Brook]

Howdy Deab,

You can definitely allow front-end submission of events with Community Events. However, it does not yet support charging people to submit events. That is a feature we are strongly considering. Please vote for it if it’s something you’re interested in.

Thanks for marking the answer correct, Marco. I am going to archive this topic since it’s resolved. If you need further assistance dean please open a new topic, we would love to help. However, in this forum we keep each topic focused on a single user, so this particular topic is not a good place to continue our discussion.

Cheers!

– Brook

[Brook]

Thanks for marking the answer correct. I am going to archive this topic since it’s resolved.

Cheers!

– Brook

[Brook]

You are welcome Keith! Good luck with your project.

– Brook

[Brook]

Thanks for marking the answer correct. I am going to archive this topic since it’s resolved.

Cheers!

– Brook

[Author]

Posts