Forum Replies Created
-
Posts
-
Oh I forgot to mention, I have a couple of ideas for what you can do in the mean time, while we wait for the new feature to be released. You could certainly try a caching plugin if you haven’t already. In theory some caching plugins could help with the initial page load. But when you page back/forth a month within the minical, it will slow your site down as it always did.
10 seconds is extremely long. A faster server would usually be able to cut that time down. 4k events is not that many, we have plenty of sites with over 10k. But, they do demand more powerful servers. What hosting provider are you using? I suppose if you’re using New Relic you might be the server admin. If so, are you pretty confident that your server and especially database are tuned to take advantage of your infrastructure?
Cheers!
– Brook
Howdy William,
Thank you so much for taking the time to research this so thoroughly, and sharing your results. I am really happy you reached out about this.
Our minical widget could use some lovely improvements in performance. A little bit back I did some proof of concept work, it demonstrated how much we could improve if we rewrote nearly all of the queries the widget makes. We now have this proposed rewrite on our docket as a priority 1 task. Those improvements will make it perform far better than it ever has, even above 4.2.6.
I wish I could say when those improvements will come soon. But, in the interest of being forthright I’m not sure when they will happen. They are in part dependent upon an upcoming feature we want to release, an annual/year view for the calendar. Thus even though we view this as a very high priority issue, it is naturally slowed down a bit by the feature that is spawning the rewrite.
I just put a couple of questions in our ticket to see if our strategist has a rough idea of when this might be slotted. Hopefully he knows something more and we can share a rough estimate with you.
Please let us know if you have any questions. Cliff will take over for me from here, to guarantee you get the fastest response we can offer.
Cheers!
– Brook
Howdy Johnny,
Andras has been pretty swamped the last little bit and asked me to take a look at this.
I think this code snippet is exactly what you’re looking for:
https://gist.github.com/elimn/dd7de019f478bd151ca14cafe7d284f1
That will add a working Gcal link to the email template. Note, the Email template does not include any “button” styling, so this is just a plain blue link by default. If you want to style it up you will need add some CSS that changes the look from a regular link to a button. But regardless of how it looks, it should work as you’ve described. 🙂
Let us know if that helped. Cheers!
– Brook
Howdy Clifton,
I would love to help you with this.
If you don’t mind I have a few more questions for you, hopefully they will help shed light on what’s going on. This is a pretty strange problem.
- Could you go to WP-Admin > Events > Settings > Tickets, and click save? I notice a few settings are missing from the system info your shared. Clicking save there should save them to your system info.
- What happens when you checkout with a non-ticket product? If you go into WoOCommerce and add a new product. Then add it to your cart on the front end, and check out with only that product in your cart, what happens? Do you get a cancelled email?
- What happens when you use a different payment gateway? If you enabled the Check payment gateway temporarily, check out with that, and then mark the order as having received payment, what happens? Do you get a cancelled email?
Cheers!
– Brook
Howdy Dominic,
Geoff mentioned to me that you might like to know when a new version of that extension is available. We just released an update:
If you download the latest version, and then perform a Manual Update you should see the reset error go away.
With regards to that one email not including data, one thing that occurs to me is that your settings inside of WP-Admin > Events > Settings > Tickets can affect things here. If the attendee record is generated only when the order is complete, which appears to be what you have selected, then the attendee data is not yet accessible. Thus, it can’t be included in the email. To solve this you could generate the attendee records/ticket upon a new order. Does doing that solve this for you?
Cheers!
– Brook
Howdy Guys,
We have just issued an update to the extension which shows the ticket details within Woo emails.
If you perform a Manual Update to the latest version which is now available, these WooCommerce 3.x errors should go away!
Simon, in the file you shared, within the mse_fieldset_update_order_meta() function I am seeing some things that I believe are also going to generate notices on your website. You will likely need to rewrite portions of that function to make it Woo 3.x compatible as well. Basically anything that treats $item as an array is going to generate notices, it could likely be replaced Woo’s $item-get_data(). There could be more things as well, I’m not a woo expert. But I just thought I’d mention it. 🙂
Thank you all for taking the time to reach out and let us know this wasn’t working properly anymore. Please let Geoff or I know if you have any questions. Cheers!
– Brook
Howdy Kevin,
Shelby reached out to me and asked if I had any ideas.
Since this is working for you at some times and not others, a couple of things come to mind. Have you enabled Month View Cache in WP-Admin > Events > Settings > Display? If so, the cache will likely contain the old version of this template. You could disable the cache while you are doing your development then reenable it once the look is finalized.
Second, there are two templates within the tooltip.php theme override you have created, one for featured events and one for regular events. Did you add your variable in both places? If you only added it in one then these changes will not appear everywhere.
Does one of those sound like they might be the culprit? If not, can you confirm that you definitely can get the URL to appear at times, but it intermittently fails?
Thank you Kevin!
– Brook
Howdy Erick,
I was hoping to release a new version before the end of the day, but it’s been a busy day and no one was available to test my fix. While I can not release a proper new version on our extensions official page, I can still share with you this release candidate for version 1.0.1 of the extension:
Event Tickets Plus Extension: Enhance Woo Order Templates
If you uninstall the current extension on your site, then download and install this one, you should see those errors go away. Alternatively setting WP_DEBUG to false is also an option, and something I’d actually recommend you do on a live site. Those notices you were seeing are not meant for live sites, rather they are meant for plugin developers like us. Hence why WordPress recommends setting WP_DEBUG to false on every live site.
Please let us know if you have any questions. Cheers!
– Brook
Howdy William,
I was hoping to have the above “pull request” reviewed by another developer today so that I could update our extension page, but it’s been a busy day and no one was available. I will need someone else to signoff before updating the extension page with the new version, however I can still share with you this release candidate for version 1.0.1 of the extension:
Event Tickets Plus Extension: Enhance Woo Order Templates
If you uninstall the current one, then download and install this one, you should see those errors go away. Alternatively setting WP_DEBUG to false is also an option, and something I’d actually recommend you do on a live site. Those notices you were seeing are not meant for live sites, rather they are meant for plugin developers like us. Hence why WordPress recommends setting WP_DEBUG to false on every live site.
I will let Geoff takeover from here. Typically we do ask that you start a new thread for separate issues like that. Our primary reason for doing that is to make our forums easy to search, if each unique issue has a unique title it helps others with similar interests find your topic. Thus our endeavor is to make things as easy as possible on future users. But, we also stretch the rules from time to time as we wish to be as accomodating as possible. So if you don’t mind opening a new topic that would be ideal, but if Geoff sneaks in here and can help you before you do, that’s okay too!
Let us know if you have any questions. Cheers!
– Brook
Howdy Jeff and Kim,
Thank you both so much for taking the time to report a suspected bug!
I just spent a good bit of time trying to reproduce your issues here, as did someone else from the team. Neither of us can reproduce this on the latest versions of our plugins. Is this now fixed for both of you as well?
Jeff, you and the thread on WP.org mentioned the /wp-content/plugins/the-events-calendar/src/Tribe/List_Widget.php file, and you both were evidently looking for something that overrides $no_upcoming_events. After that variable is declared the extract() function can override this variable. The extract function will take any arguments passed from the widget or shortcode, such as the no upcoming events one, and override/declare any missing variables. At least, in theory it does this, and it is working great for me and my fellow tester. On both of our systems the “no upcoming events” message is displaying in a wide variety of scenarios. Hence why we are wondering if it is fixed for you now too.
Please let us know if you have any questions. Cheers!
– Brook
Howdy Kathryn,
Quick update on this issue. I think there is a decent likelihood that this is a plugin conflict, however it happens when the EA record is created. Basically a plugin is changing some data that we save to the database. Thus the data will continue to be malformed even after the conflicting plugin is deactivated, because the problem happened when it was initially saved.
That said, I also think there might be an easy solution to this problem. We are not able to reproduce it on our end, but looking at the code I can see a way we might be able to protect against this sort of conflict. Would you be interested in altering a line of code within the plugin and seeing if this issue goes away for you? If it does, we can include this simple fix in an upcoming version of our plugin, and prevent issues like this regardless of how they crop up.
The code you could change is inside of /the-events-calendar/src/Tribe/Aggregator/Record/List_Table.php. On line 288 in that file you should see:
$origin_instance = Tribe__Events__Aggregator__Records::instance()->get_by_origin( $origin );
Could you try changing that to:
$origin_instance = Tribe__Events__Aggregator__Records::instance()->get_by_origin( $origin ); if ( null === $origin_instance ) { continue; }And now revisit the page that the error was appearing on. Does the error go away. Does the page look and behave normally now?
Cheers!
– Brook
