Forum Replies Created
-
Posts
-
Howdy Vincent,
I would love to help you with this.
It sounds to me like you do not yet have an ecommerce store installed and configured on your site. Checkout our Events Tickets Plus: New User Primer for a guide on all the steps you need to do when first installing that plugin. Specifically it sounds like you missed Step 4. The most common Ecommerce platform is WooCommerce, and it has a lovely guide for how to install and configure it. Doing this should complete Step 4 of that tutorial.
Does that sounds like the issue? Does installing Woo add the ability to sell tickets?
Cheers!
– Brook
Howdy Bartek,
I would love to help you with this.
It is very likely that performing a Plugin: Manual Update will solve this problem. As the tutorial their outlines it basically entails deleting the tickets plugin folder, and reinstalling. This should not remove any data. However, WordPress always recommends making a backup before updating (Tutorial: Updating WordPress and Making Backups), whether it’s a manual or an automatic update. Usually I don’t because it is rarely needed, but that one occasion you do need it you are really going to regret not making one. So use your judgement here.
Does that all make sense? Did manually updating/reinstalling the plugin fix this? Please let me know.
Cheers!
– Brook
Howdy tadl,
That’s awesome you got this setup before. I’m actually wondering how you did it as well. 😀 Messing with permalinks can be some pretty nasty business. In my experience altering the structure has all manner of unintended side-effects and breaks things like the iCal export. If you managed it on a different site I would love to know how. I have yet to come across any plugin or bit of code that could do it cleanly, but I definitely have not tried them all.
I wish I could be of more help here 🙁 . If you can share the plugin list/configuration of relevant plugins, or any custom code run on the existing site, I might be able to help more.
- Brook
Howdy ycf,
I would love to help you with this.
PHP message: PHP Fatal error: Call to undefined function tribe_is_week() in /var/www/vhosts/you-can-fight.com/httpdocs/wp-content/themes/Avada/functions.php on line 261
That specific error is coming from the Avada theme. Avada evidently expect Events Calendar Pro to be installed and activated on your site. If it is not active this error will appear. Have you tried activating Events Calendar Pro? Do a lot or all of these errors/glitches go away?
Thank you for sharing that one error message above. If there are more error messages after activating Pro, we you mind sharing those ones as well? That will shed a lot of light on this issue.
Cheers!
– Brook
Howdy Chris,
I would love to help you clarify this.
Manage different rooms at those locations (e.g. Lobby, Conference Room, Lecture Hall)
It sort of depends on what you need to manage. If you are planning to use the RSVP or ticket sales aspects, you can sell tickets/book RSVPs for each location separately. Is that what you were thinking, or did you have a more in-depth type of management you were hoping for?
– Allow co-workers password protected access to enter own events and check the event schedule
That is totally possible. Individual events can be given a password by default.
Or, if all of you events are private you could just password protect the entire calendar. This willl require a slight modification but is totally possible to do.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Awesomesauce!
I’ll leave this open for a couple of weeks just in case you have any questions about the Router, should you go that route.
It’s been a pleasure, Aurélien.
- Brook
I am stoked it is working as you wanted! Thanks for getting back.
I need to start testing more with deletes, changes and additions but I just imported 174 events in one swoop on the dwh site… All recurring events
One thing I should mention is that iCal is an event creation format, not a deletion one. It contains no information about recently deleted events. Thus deleting an event from one site will not delete it from another.
We are considering an option that would just assume any event no longer present in a feed has been deleted: Option to remove events not present in a reimported iCal feed However that will require your iCal feed to contain every event on the site, potentially thousands of events. And the site which imports it might have trouble attempting to import thousands of events. It all depends on how fast the server is.
For now the best option here is to delete an event from both sites if you need to delete it. Typically people don’t delete events very often, so hopefully that won’t be too much of a manual hassle for now.
PS. I was using EM with ESS add-on till now and decided to swith everything to TEC. Mostly because it is such a pain to get EM to look nice in the theme and for the EM Calendar to perform. I have worked now for a long time with WP and php but still, maintenance becomes something to be afraid of if I hack the plugin so much. I really like the responsive little tricks you guys do with TEC. One hurdle is to let go of ESS, that is a much more complete XML interface then iCal (eg will also get the event image!). Why not add it to TEC for TEC2TEC syncs? It is a free standard (http://essfeed.org)
That’s a great idea! I just added this feature suggestion: Add ESS feed support
Cheers!
– Brook
Thanks for your understanding!
also if i export to excel file
The fields are in gibberish
See attachment..That is basically a bug in Excel. You have to run through a few extra steps in Excel to work around this. If you do those steps it should import properly. Did that work?
- Brook
No worries. I will do my best to help. We are a bit limited in how much exact code we can provide, just due to the extraordinary amount of time it usually takes to provide exact code (we would go bankrupt). But I’ll do my best.
It looks to me like you should find this line:
function mse_woocommerce_order_item_meta_end( $item_id, $item, $order ) {And insert this new line directly below that:
echo '<br><b>Ticket ID</b>' . get_post_meta( $order->id, '_unique_id', true );
And I believe that will do the trick! Does it?
Cheers!
– BrookHowdy Eileen,
Great question.
By default Editors do not have the “import” capability in WordPress, and can thus not mass import any sort of data including Events. If you wish to change this though you can do so using a plugin like User Role Editor. Simply add the import capability to the Editor role and you should be all set.
We actually have a feature request for this you might be interested in voting on: Allow non-admins to import via CSV But it is doubtful we will ever change the default here because doing so would run contrary to WP’ best practice.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
I forgot to ask: If you don’t mind sharing, who is your web host? Could you share the specs of your server if you know them?
– Brook
Howdy Kgemmel,
I would love to help you with this. Performance is one of my favorite things to assist with. 🙂
We are caught between a rock and a hard place when it comes to queries like this. WP best practice strongly encourages plugins to not create new database tables for postmeta data. We follow the “best practice” here and store all our event meta data, including start and end dates, in wp_postmeta. This makes our plugin broadly compatible with third party plugins. However, wp_postmeta is extremely slow. All dates are stored as strings. Further this table can get huge fast, and must usually be joined to wp_posts.
I have examined that query and run some tests. I do not see much of anything that can be done to optimize it, except us rearchitecting the plugin to violate the above WP best practice. This is an idea we have frequently tossed discussed. We would love for our calendar to scale better on slower servers. But, for the extreme majority the current implementation is fast enough, and best of all it plays nice in the WP ecosystem. So to date we have decided to keep things as they are.
I just opened up a feature request regarding the above, just to see if gets any traction with the community. If you wish to vote on it please do: Improve performance by storing event data in separate database table
I noticed on some other threads that selecting the cache option in the admin settings has helped in some cases but it doesn’t seem to do the trick here.
The query you’ve shared does not appear to be a Month View query. Our caching system is exclusively for the Month View and won’t speed up anything else.
In an attempt to speed things up we tried indexing those particular tables that get queried, as they are not usually indexed by default, but that didn’t seem to help as it looks like it is building a temporary table with all the joins every time and then scanning that which is a huge amount to go through and consequently quite slow.
Indexing will not help here unfortunately. It’s the nature of this type of query.
There are currently just over 2000 events and were hoping that removing them will help the issue. I’ve also noticed that wpengine has given some people grief with this plugin. We are NOT using Wp engine but if there are any settings we can adjust on our server to help solve the issue let me know.
A couple of years back WP Engine did have some performance problems that were very specific to their platform. It was fixed back then.
Technical details if you’re interested: One of our performance optimizations was to make the WHERE clause exclude everything it possibly could. This made the query’s text unusually long, but also made it execute much faster. WP Engine was measuring the text length of queries, and deprioritizing lengthy ones. This made many queries that we optimized to run faster on most platforms actually run slower on theirs. We worked with WP Engine for a while and helped them identify the problem. I am happy to say this issue was solved quite a while back.
We still get the occasional thread mentioning WP Engine and performance problems. But thus far every topicI have seen is like yours, where the posts database is enormous (your query examined nearly a million rows) and is not actually a WP Engine specific problem.
If you have any other suggestions, patches or ideas please let me know.
I have a few:
- Are all of your WP Tables InnoDB ?
- Do you have control over the MySQL server where you can alter the config file?
- If so have you tuned it? Here’s a decent article on tuning InnoDB.
- In particular you will want to set the innodb_buffer_pool_size to be as large as you reasonably can.
If everything is already tuned to as fast as it can be then you might just need a faster MySQL server. For run-of-the-mill hosting plans this will entail getting a nicer general hosting plan, perhaps at a competing web host.
Does that all make sense and help clarify what’s going on?
Cheers!
– Brook
Howdy Saha,
Thank you for reaching out about this. I believe you are spot on, it would seems that there would be a super momentary delay between when we retrieve the last used ticket ID and when we increment it. If a second customer purchased a ticket between this millisecond window, in theory they would get a duplicate ticket number. That’s crazy!
This is definitely a bug we’d like to address. I really appreciate you bringing it to our attention. I do not really have a solution for now, we will just have to wait for this to get patched in a future version. Once patched, all new tickets should get a unique ID. I am very sorry for the inconvenience.
We will let you know once a fix is released. Please let me know if you have any questions. Cheers!
– Brook
