Forum Replies Created
-
Posts
-
Howdy Colin,
I would love to help you with this.
Is it possible to achieve this through configurations panel on dashboard or it is some customization required at code end
Good question. This is definitely going to require a decent measure of coding. But I’d love to help point you in the right direction to start.
First thing I would do is add the extra selector to the tribe bar. We have a great tutorial on modifying the Tribe Bar: Customizing the Tribe Bar . With that in place you will now have a new variable submitted with the tribe bar, but it does nothing.
Personally what I would do is tap into the tribe_pre_get_posts actions, which behaves identical to the infamous pre_get_posts but the tribe_ one will only run on events queries. From there I would check if the var is set for your end date tribe bar. If it is I would add an ‘end_date’ query var to the query.
This might be all you need to do. However, I could see the potential for some lovely complications that might happen. This sort of modification will require a lot of testing and might end up having to account for a bunch of unforeseen complications. Only way to know will be to build it.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy Dualwerk,
I would love to help you with this. It’s going to be a bit complicated to do what you want, due to the fact that will involve directly editing the SQL of a bunch of WP_Queries. But it’s doable if you’re comfortable modifying such things.
The first thing I would do if checkout Tribe__Events__Query::posts_orderby() . This function is attached to the ‘posts_orderby’ filter in WordPress, and it does all of the ordering for our event queries. You could build your own function in the same faction and attach it to the same filter, then insert or modifying any of the SQL sorting logic to do as you please.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy John,
I would love to help you with this.
I am guessing you probably have a month somewhere on your calendar with many hundreds of events. And when you visit that page this error happens. The Query that your server is killing determines which category each event is in. It runs once each time you load month view. Each event in the month has a numeric ID like 5889. If there are hundreds of events in the month, there will be hundreds of IDs in the query. And with enough IDs you could get a query that is 53138 characters long as the error states.
Are you on WP Engine perchance? They are the only ones I have seen kill “long queries” like that. When you google around for that error so far the only host I’ve seen associated with it is WP Engine.
You are probably safe enough to ignore this. We are working on some performance optimizations, and a side effect of them will likely be fewer IDs included in that tax query. The only option would be to find which Month is generating this error by examining your logs in more detail, and then deleting some events from it until the error goes away. WP Engine can handle only so many events in a given month.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy Ruben,
I would love to help you as best I can,
From what I am understanding you have two requests:
- How do you embed a tickets area in a non-events page?
- How do you list a non-events page on the calendar?
In order to do either of those you are going to need to do some serious PHP development/programming. It is possible, but it’s going to require an abundance of time and ability with programming. It would be far easiest so modify the template for events to look as you need ( Tutorial: Themer’s Guide ). But even that will require some experience with WP Theming. One way or another it will not be possible to do with a GUI like page builder, it’s going to require a decent amount of work in HTML/CSS/PHP. And the easiest way by far would be use our themer’s guide to modify the single event page to look as you need.
Does that all make sense? Knowing that do you think a different route is going to work better?
Cheers!
– Brook
Good question. I have to guess a little bit because I do not have a corrupted database on hand to test with. But I believe it will delete all recurrences that are greater than 2 months out when set to 1 month.
Ordinarily decreasing this setting would not delete recurrences, it would simply prevent further ones from being created until you are ~1 month out. However, the cleanup plugin is triggering a rebuild, and in theory that would cause the extra recurrences to disappear. If it does not, then editing an event series and hitting update definitely will cause that series to delete future instances.
Depending on your needs this might be a moot question. If your calendar was running fast enough before the update, and it’s only since the update that things slowed to a crawl, then deleting those extra 23 months is not necessary to get things back to speedy.
Please let me know if you have any more questions before proceeding. Cheers!
– Brook
Howdy again Ashleigh,
Typically modifications like this will go in your theme’s functions.php file, which will be located in your theme’s folder. It’s just an easy spot to put visual changes like this in.
Are you able to find that file in your theme folder?
Cheers!
– Brook
Howdy again Clair,
Are you still seeing this problem? We patched a few bugs recently and I am not able to reproduce exactly this.
There is one piece of behavior that might be affecting you here on second glance. If you create an attendee field and name it something like “Meal Choice”. Then some people purchase a few tickets and select their meal choice. Finally you rename the field Meal Choice to something else, it will hide all of the data already input into that field.
The data is not actually deleted, and renaming the field back to Meal Choice will cause it to appear. Initially you said your developers had confirmed that this data was truly deleted so I did not suspect this was what you were referring to. However, on second look through this topic I am wondering if the developers might have just missed the data. The database is very big, and unless they knew very specifically what to look for I could see them missing this. Does this sound like it might be the problem you were experiencing?
Cheers!
– Brook
Howdy Max,
Hey I am happy that snippet helps!
Google Calendar unfortunately will continue to be limited to a single event for now. The API we use to add events can only export a single event at a time. 🙁
It’s my pleasure Max. Please let me know if that answers your questions, or if you have any more. Cheers!
– Brook
A fair point, after having a second look at our product page it only briefly mentions this in the first few paragraphs. I agree, it should be abundantly obvious what’s required and what an ecommerce platform is. I’ll pass that info on to the folks in charge. Thank you for the feedback!
- Brook
Interesting. That could be part of the problem. As George mentioned our most recent update for pro is 4.2.2.1. You can download a fresh copy of it from this website, in the upper right you should see “My Account” then inside that menu “Downloads”. Go there to download the any versions of a plugin you own. If you download it this way you will need to perform a Manual Update.
Further, once all this is over you can input your license key in WP-Admin > Events > Settings > Licenses. Then you will get automatic updates to the plugin via WordPress, and can simply hit update in WordPress to get the latest version.
Installing the latest version of Pro should stop any “runaway recurrences” from getting created. And then installing the cleanup Tool George mentioned should cleanup duplicates. This might just be the solution you’re looking for.
- Brook
