Forum Replies Created
-
Posts
-
Howdy John!
That’s a good question. I can see how it would be confusing to you. Usually people who purchase WooCommerce Tickets are already running WooCommerce, have it setup and configured. In their case they already have configured their template to have a Cart link and likely already have products so it all makes sense. But you are not in that circumstance at all from the sound of it.
Both of those issues are WooCommerce issues, and unrelated to our ticketing plugin. Which is probably why you are having trouble finding documentation about them. But there’s not to worry about that now. You already solved the cart link issue by adding a link. Here is a solution to your redirect issue I just found on the WooCommerce website (click here).
Does that all make sense? Will that work for you? Please let us know.
Cheers!
– Brook
How
Howdy Communicatio,
Thank for sharing the screenshot! It helps me see what you are talking about. Could you share a link to the page in which you are seeing this on as well? That might help shed more light on the matter. What you have described and screenshotted is definitely not a bug I’ve ever seen before, but some further investigation might reveal a culprit.
Cheers!
– Brook
Howdy Allan,
I just checked in on our logs. It looks like as of Thursday we are 68% done. But of course in software development all estimates are best guesses, as there are always unknowns. A bug can crop up at any minute and delay you considerably.
Currently it is on track to be released with version 3.12. But, if something unforeseeable ends up delaying it, it could take longer.
I hope that information helps!
– Brook
Hello Joey!
That is an easy way to list a bunch of events. I like it. We do not have such a compact overview built into our plugin. So buying it will not get you that list. However, it would really be very easy using our APIs and templates to build such a view. But, you will need to know some PHP and CSS to get it looking exactly the same.
Does that all make sense? Will that work for you? Please let us know.
Cheers!
– Brook
Howdy Brandon,
1.) I am unable to search events by Start Date on the admin side. It generates no results when I ask for events for a specific date.
That is a known bug 🙁 . There is a fix though. If you open up events-calendar-pro/src/Tribe/APM_Filters/Date_Filter.php, on lines 68-73 you will see:
if ( $key === 'ecp_start_date' ) { $field = 'eventStart.meta_value'; } if ( $key === 'ecp_end_date' ) { $field = 'eventEnd.meta_value'; }Replace those with:
if ( $key === 'ecp_start_date' ) { $field = 'tribe_event_start_date.meta_value'; } if ( $key === 'ecp_end_date' ) { $field = 'tribe_event_end_date.meta_value'; }We will get this patched in an upcoming release as soon as we can. But of course you can patch it yourself in the mean time by following those steps.
2.) For some reason a venue was duplicated on a couple of other events that were totally unrelated to the one event that was created. How could this have happened?
I am not sure I follow. Are you saying that you create a venue for one event, then later discovered two event which had no venue were now assigned to that new venue? I have no idea how that could happen. But perhaps I am misunderstanding?
Please let me know. I want to be of further assistance. 🙂
Cheers!
– Brook
Howdy Carla,
It’s nice to meet you. I am happy you reached out. It’s an interesting conundrum you face. Probably the only time you will want to reimport something you have deleted is during testing, but that’s the phase you’re at and you understandable do wish to reimport.
You can turn that feature off. I wrote a quick snippet yo do just that. Paste it at the top of your theme’s functions.php file, underneath the first line “<?php”. If your theme does not have a functions.php file, go to your theme folder, create a new text document file called “functions.php”, and paste this text in the first line of the file “<?php”. On line 2 or 3, paste that snippet.
https://gist.github.com/elimn/13b32fb7763826df78d2
This will make any event you delete now truly delete. However, you still have some undeleted events in your database and they’re not showing up anywhere. With that snippet in place you can now properly delete them, but you will have to use some PHP. First we need to get a list of any iCal events that are hidden but not fully deleted. To do that run this SQL in your MySQL database:
SELECT ID FROM wp_posts WHERE post_type LIKE 'deleted_event'This will return a list of post IDs that you deleted. My database returned 857, 858, and a few others. To delete those I temporarily added these lines of code to my functions.php file:
wp_delete_post(857, true); wp_delete_post(858, true);That fully deleted those two posts. Now when I reran the iCal imported they reimported. But first, I had to remove the above two wp_delete_post lines from my functions file as those only needed to be run the one time. If you have access to your PHP console you can of course do this even easier, but not many have access so ignore this sentence if you don’t think you do.
Did you follow all of that? I am sorry it is not super easy to undo at this point. We did not really think about people in your shoes while building this who might be testing and actually wish to not permanently hide a given event. Please please let me know if you have any questions. I am here to help. 🙂
Cheers!
– Brook
Howdy Miah,
Is the knowledge base the only place you have your functions documented at this moment? Are there any other sources I should look into for documentation?
Our API documentation (AKA Technical Docs) is where the functions are documented. Our Knowledgebase on the other hand has tutorials and guides with practical examples of how to use our API. They are pretty tightly integrated, but still slightly different. The API Documentation is actually a curated version of our inline docs that exist in the code. The inline docs are the most extensive and can be found in context within each file of our plugin.
We’ll simply create a child object (post type) to Events and then use front-end forms to allow our members to sign up for the events, which will dump the data to the new child object.
That sounds awesome!
I will keep this ticket/topic open in-case we need to ask questions as we develop.
If you don’t mind, would you please open a new topic for each ticket? That’s part of our forum rules here. Our reasoning for this is not because we enjoy creating limitations. Rather, our tools here are built around a single issue per topic (IPT). Having one IPT means that we can track all issues and make sure every single one is resolved. It also means that users with similar issues are better able to search and find past topics because they all have unique titles. Finally and perhaps most important of all, we have found that a single IPT helps get our customers faster response times. 🙂
Please let me know if you have any more questions pertaining to this Miah. Cheers!
– Brook
Howdy again Miah,
That sounds like a good plan.
Our code is very well documented. Every single public function is documented in the code and on the website. Many of our classes and their public functions have inline documentation as well. We also have a sizable Knowledgebase which has many tutorials and articles to assist with using the API.
Now I wish I could enthusiastically say we have everything documented, but there are is one weak area we are working to improve. We have an enormous amount of Hooks and Filters sprinkled in useful places, which makes it easy to develop for. But, at the moment we do not have a comprehensive list of them. Of course even without a list you can still find them the old fashioned way, but I do wish it was even easier than that.
Finally, we will be here as well to help answer questions.
Please let me know if you need anything else. Cheers!
– Brook
Interesting. Well I am glad that works for now. Please let us know if you need anything else.
Since this particular issues is resolved I am going to archive the topic. Always feel free to open a new one.
– Brook
Definitely a temporary solution. Thanks for letting us know Christoph. I hope you don’t mind, I nabbed your system information from a previous post of yours. I will use that as well. We set aside some more time for further testing today, so I will let you know the result.
Cheers!
– Brook
I just wanted to give you all an update. We have done some testing here and no one was able to reproduce the issue yet. But I have a couple more ideas I’d like to try. I will keep you updated.
Thanks again for sharing your temporary workarounds to this problem. I am happy it is not currently affecting your sites while we investigate.
– Brook
That is strange. Thank you for working between the two support teams, ours and your themes. I know that’s not usually very fun or easy. If there is anything I can do to ease the pain please let me know.
I’ll wait to hear from you. Cheers!
– Brook
Thank you guys, you are very kind!
I am happy 3.10 works for now. But we are still looking into this. No one else had seen any reports of this problem, nor was anyone able to reproduce. But we of course want to investigate further. Hans-Gerd shared the system information for that setup. Would everyone else be able to do that as well?
You can your system information and paste 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) That will give me a lot of extra information to help diagnose the problem.
Thanks again!
– Brook
