Forum Replies Created
-
Posts
-
Howdy OngKar,
I would love to help clarify this.
First up let’s tackle WooCommerce/EDD/Shopp/WPEC tickets. These four “legacy” plugins were combines into one plugin: Event Tickets Plus. You can basically ignore them, Event Tickets Plus is the new version of them. These allow you to sell tickets on your website through one of the four Ecommerce platforms. You will first need to setup and install one of those Ecommerce platforms, which will allow you to sell things on your website. The extreme majority of people choose WooCommerce. From there you can install Event Tickets Plus and sell tickets as well through your site.
Eventbrite is a bit easier to setup. You do not need to setup an ecommerce site, nor any of the associated costs. Instead you signup with the Eventbrite service. Then you add events and tickets to Eventbrite, and you can sell them from there. They take a percentage of every ticket sold. A lot more info can be found on their site. Our plugin, Eventbrite Tickets, ties into this service seamlessly and allows you to publish events from your site onto Evenbrite, and also add Eventbrite ticket. You can do all of this through WP Admin, and copies of those events along with ticket purchase links will be on your website.
Community Tickets is an addon. To use it you must already have Event Tickets Plus and Community Events setup on your site. With these three plugins it becomes possible for you site’s visitors to add tickets to events they submit to your website.
Does that help clarify things? Do you have any more questions?
Cheers!
– Brook
Howdy Cindy,
I am sorry this is giving you troubles. I would love to help you figure out what’s going on.
Would you mind grabbing your system information 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) That will give me a lot of extra information to help diagnose the problem.
Cheers!
– Brook
Howdy Ben!
That might help prevent Google from indexing new pages, but the old ones will still be in their results. If you wish to hide anything from Google you can do so by adding a robots.txt file to your website. Next time Google indexes anything on your website they will look for this file, when they see it they will remove any pages you’ve told them to. If all of your events are in example.com/events/, then put this in your robots file:
User-agent: * Disallow: /events/ Disallow: /event/Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy alchetecwebdev,
I would love to help you with this.
Were you running version 3.1 (three dot one) or perhaps 3.10 (three dot ten)? If you are running 3.1, I would advise you don’t updates all the way to 4.0 just yet. I would recommend you first update to 3.5.1, then to 3.10.1, then finally to 4.0.4. You can download each of these files from this website. Go to My Accounts > Downloads, select the proper version number and click Download.
Does that sound applicable to your site? If you give that a go, including redownloading 4.0.4, does the error go away?
Cheers!
– Brook
Howdy Birgit,
I would love to help you with this. Without being able to examine the webpage in question I can only guess as to a solution. But adding this CSS might help things shrink:
.table.tribe-mini-calendar td, table.tribe-mini-calendar th { padding: 0; }Does that all make sense? Does that work? If not, can you share a link to the page with this issue?
Cheers!
– Brook
Howdy Paul,
Good question. It sounds like Event Tickets Plus will actually be a nice drop-in for your setup. What does is actually pretty simple. When you add a ticket to an event with Event Tickets Plus, the plugin generates adds a new virtual/downloadable product to the WooCommerce store. When a customer visits the event page, there is a section for adding that ticket/product to their cart. Once added to their cart everything is handled by WooCommerce, because tickets are just another product in the store. Reports, payment, sales data, everything is native to WooCommerce. So if you already have a reporting solution in Woo that you’re happy with, it should support Event Tickets Plus too. Any tickets sold with our plugin will just be new sales data alongside your old, along with any other products you still sell via Woo.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Howdy Liz Roberts,
Great questions. I would love to help you with this. I’ll answer these one at a time
1) Is it possible to allow a user to register for tickets/events in one transaction? I assume yes and that you would just add multiple items to your “cart.”
Yes it is possible, it functions exactly how you assumed.
2) Does this extension include the ability for customers to create an “account” and login for future transactions?
The extension adds a new type of product to WooCommerce – tickets. They behave in the same way as every other product in the WooCommerce store, the only difference is the “product page” is the event itself. \
WooCommerce handles checking users out and their account information. So if you setup WooCommerce to allow registered users, Event Tickets Plus is also setup. However you configure WooCommerce it will apply to Event Tickets Plus as well. In short: yes.
3) What does Tickets offer in the way of running reports for lists of various customers? Example: Customers in a particular region, customers with a particular job title, customers who have taken a particular course, etc.
Like the above question, this is all handled by WooCommerce. Whatever reports WooCommerce generates will include tickets as well. Any third party WooCommerce reports plugins should almost certainty be compatible with Tickets too.
4) Does Tickets work with the WooCommerce PO gateway: https://www.woothemes.com/products/woocommerce-gateway-purchase-order/
It should. If for some strange reason it does not though, keep in mind that both we and WooThemes offer full refunds up to 30 days after purchase. So if something isn’t working or not what you expected, you can get your money back. 🙂
Does that answer all your questions? Can I clarify anything? Please let me know.
Cheers!
– Brook
Howdy Alex,
I would love to help you with this. It sounds like you are using Event Tickets Plus with recurring events, and it’s giving you trouble. Event Tickets Plus does not actually support recurring events, but we are building compatibility. Specifically it does not yet allow you to purchase tickets for only one of the occurences in a series. Rather it treats the series as entire course or event that only needs one ticket for access to every day in the series. So we need to add functionality to make it so that people can purchase tickets for only one day out of a recurring series.
Does that all make sense? Does that answer your question? Please let me know.
Cheers!
– Brook
Good question. The event data is stored in your database, so deleting the folder should not touch your data. The folder you want to delete is located inside the WP folder:
/wp-content/plugins/the-events-calendar
Let me know if you have anymore questions. Cheers!
– Brook
Thanks for chiming in Barback! That is an easier solution.
Using CSS like that does prevent it from being easily visible. But the information is still there if a competitor or interested party investigates, they can still find out how many tickets you’ve sold and how many total are available. The last person who requested this was quite privacy conscious, so I only thought to share the same method I shared with them – which does fully remove the info from the public. But if you’re really only interested in masking over the data then Barback’s solution is much easier and does the job perfectly.
As always, let me know if I can be anymore help.
– Brook
Howdy Andreas,
I am sorry you got hit by that bad 4.0.5 release. We try to react extremely timely to any security vulnerabilities. But we obviously were too hasty this time, especially considering the vulnerability was not publicly known and there are no known cases of it being exploited. We should have tested it a bit more.
To do any kind of manual plugin update, reinstall, or downgrade, you should delete the plugin folder first. WordPress itself deletes the folder before copying over the fresh one from the plugin .zip file, that’s just how updates work. However, that said WordPress also recommend that do a backup before updating. Whether that update is “automatic” through the WP Admin, or manual, it is highly advisable to first backup WordPress. Many people choose to not backup and just update anyway, but there is always a small chance of catastrophe when going this route.
In short, I am advising you to first to backup (Tutorial: Updating WordPress and Making Backups) just to be doubly safe. From there delete the The Events Calendar plugin folder, and install the latest zip from WordPress.org: The Events Calendar. And you should be all set with no more 4.0.5 errors.
Does that all make sense? Do those steps fix it? Please let me know.
Cheers!
– Brook
Howdy Pedro,
Time.ly allows you to export events as .ics iCal files. We off the iCal Importer which allows you to import those .ics files. If you have 900 events I would recommend exporting them in batches. Many servers are not able to import 900 at once, but most can handle 100 or so pretty easily.
That sound like it will do what you need?
Cheers!
– Brook
Howdy Hans,
Thanks for your detailed description and testing without that snippet. That really narrows it down.
It is very probably this line of the snippet that is causing issues:
$order->update_status( 'completed' );Right there the status is being pushed to completed anytime the thank you page is being shown. You will need to add some logic to detect what the order_status is using $order->has_status(), before updating it. I am not familiar with the Mollie plugin, but from the sound of it the order status may be ‘cancelled’ in your case. You can use $order->get_status() to find out what the status is and work from there.
Does that all make sense? Will that work for you? Please let me know.
Cheers!
– Brook
Oh I did not think about that. Find this line:
function filter_events_title ($title) {And add this underneath it:
global $wp_query;If anything can fix this that can. However, it might just change the error message you get, or it might show an erroneous date in the <title>. This is because $wp_query has not been fully setup at the point the <title> is output. In order to work around this it will get ridiculously complicated. 🙁 It will require a very advanced knowledge of PHP to either setup the date, or to use ob_start() to capture the output of the page and try loading the <title> date afterthe page but outputting it first.
Let me know how it goes. Hopefully the simple fix I detailed at the outset is all we need!
You’re very welcome. We really value your contributions in helping us find bugs.
- Brook
