Forum Replies Created
-
Posts
-
Hi! Really sorry this slipped through the cracks, for some reason I didn’t get an alert when you replied. Do you still need help with this?
It doesn’t come across as a crazy rant at all, believe me when I say that we appreciate your frustration 🙂
Also, I definitely did not mean to imply we will not address this. I’ve asked one of our developers to look into this and simply wanted to offer you a possible workaround in the short term so that you could keep going – realistically the assigned developer may not be able to leap on this issue today and it could be next week before we get an answer so I thought it was worth looking at ways to keep things ticking over in the meantime and avoiding unnecessary disruption to your routine as far as possible.
Regarding the exposure of unpublished drafts, I’m not sure in what scenario they might be exposed that would be problematic for you – but the role of a draft does seem to me to be a good fit for what you are trying to accomplish here. If it’s unpalatable for any reason then I’m afraid there aren’t too many other convenient ways of achieving this that I am aware of.
Last but not least we are not hoping issues will go away by ignoring them. We are focused on a large scale rewrite and that has had the unfortunate side effect of meaning we have delivered maintenance (“bug fix”) releases less frequently than normal – but we are doing that because we believe it is the best use of our resources and is in the best interests of the wider community of users.
Yeah there are a few strange artifacts there – I’m not completely sure if they are being caused by your theme or another plugin though. To determine that you would I’m afraid have to:
– Deactivate all non-Modern Tribe plugins
– Switch to a default, unmodified theme (such as Twenty Twelve)And check the submit form at that point, then reactivate everything one at a time and see when those artifacts come back to life. I hope that makes sense but let me know if you need any clarification.
No problem – should it help, when I tested yesterday it seemed that if I navigated back to the home page I ended up at yoursite.com/events rather than yoursite.com – so my impression was that this was not specific to The Events Calendar but rather the way the installation had been configured.
Certainly do post back if you need more help though.
That’s strange. I can see that a Javascript error is occurring when I try to navigate:
TypeError: data.match(…) is null
That commonly indicates that there is a conflict somewhere along the line, so, could I ask you to carry out our standard troubleshooting steps?
- Please ensure that your Modern Tribe plugins are up-to-date and in-synch … for instance if you are using The Events Calendar 2.0.11 you must also use Events Calendar PRO 2.0.11
- Deactivate all other plugins and change your theme to a default, unmodified one such as Twenty Eleven or Twenty Twelve
- Now test to see if the problem still exists
- If the problem has been solved by these steps, start reactivating everything one-at-a-time, testing at each point to see if the issue has returned
- If the issue does return, take note of whichever plugin (or theme) you reactivated immediately before it started again – it’s likely there is a conflict with this item
Would it be possible for you to workaround this in the short term by using the Draft post status instead of setting the visibility to Private?
Indeed it would and I can definitely replicate this. Bear with me while I check out a few ideas on this one.
OK – all I can really suggest is trying again and following the instructions in the Codex article verbatim.
It’s not unusual to install WordPress in a sub directory but have it show as if it was in the “root” and I’ve seen other installations that use The Events Calendar do this successfully.
I’m not sure either – what I can say is that it works for me and a couple of other users, so it’s puzzling that it isn’t working for you.
If you set up a test environment with just a default and unmodified Twenty Twelve theme – and The Events Calendar, WooTickets and WooCommerce (latest versions of each) installed and activated are you able to see this working there?
As you can appreciate, we do have limited support bandwidth and so we unfortunately can’t always take a hands on approach with what are after all non-standard customizations (you could also consider hiring a developer/designer for support here, if you are really stuck).
Great! Yes I’d strongly recommend using a recent (2.0.x) version of WooCommerce with WooTickets 1.0.1.
Since it looks like we are all sorted here I’ll go ahead and close this thread. Thanks all 🙂
Hi Wolfgang.
Great questions, let me try to answer them in turn.
The customer can buy 3 different ticket types: daily ticket day 1, daily ticket day 2, daily ticket day 3, festival ticket (all days)
WooTickets has no inherent concept of a ticket that covers multiple events (which is how each individual day would be seen) – so this is one area where you might need to do a little customization or else think of a workaround.
his personal data is only used for the payment process. the tickets shouldnt be personalised. even the customer must not give attendee data for each ticket he buys. that means: if a customer buys 20 tickets, he only have to give personal information one time
This is indeed how the current version of WooTickets functions. One person purchases x tickets and is not solicited for extra information about the individual attendees.
if the customer bought the ticket, he gets an automatic email. even we get an email. if we provide bank transfer as payment method we are able to change the payment status and send the ticket manually.
Again this is generally how it works, except that as the tickets are set up as regular (shipped) WooCommerce products the order may not be automatically marked as complete (and so that may have to be done manually even where the payment has been made via PayPal or a similar service), though this depends on your choice of payment gateway and some users have found a convenient workaround by setting the product type to virtual/downloadable.
every ticket has a valid date (from-to?) which is saved in the database (we would develop a scanning software that checks the unique code at the ticket against the database by comparing the current date with the valid date stored for the ticket)
So currently the ticket is pegged to an individual event and so it would definitely be possible to find the events by querying for the event corresponding to the ticket.
However, I don’t believe those dates are recorded immutably against each ticket sale so if the event dates changed after the sale was made then effectively so would the ticket dates.
it is possible to customize the style of the e-tickets even the whole frontend and e-mails.
It is indeed possible. Customizing the PDF e-tickets in particular can be quite involved however and isn’t something we would be able to help with.
we also sell hard tickets via presales stores. for them we have to generate a couple of unique id’s to print an barcode/qr code on our tickets. the tickets can assigend to some dummy users.
Again WooTickets isn’t set up specifically to facilitate this, so you might need to investigate how best to accomplish this.
is it possible to use all woocommerce payment extensions with this plugin?
Absolutely. WooTickets builds on top of WooCommerce but fundamentally the checkout experience and payment system is the same is it is without WooTickets.
Regards,
Barry
OK, thanks for clarifying – I think I’ve got a good handle on what you want here: that is, to add a Submit Event link next to the Event List and Calendar buttons – but let me know if I’m off-beam there.
Just to explain why this isn’t included by default: it’s simply because not every site owner would want it to be present and, of those who do, there are probably a wide range of differing needs as to what views should include it and where it should be positioned. For that reason anything like this is essentially left open for people to customize as they would like – I hope that gives a sense of why we do (or do not) include certain features.
So the first thing to do is familiarize yourself with our themer’s guide and also this tutorial on template overrides. Both are definitely worth reading before you embark on any changes like this 🙂
Here is a snippet showing some code you can find in the gridview.php template: http://pastebin.com/2xiHVjgv
You would want to add an extra link in there and that might look like this: http://pastebin.com/0GYwQCTr (as noted in the snippet, do change the URL to whatever makes sense in your case).
Does that help here?
Just to clarify:
…but this would mean that these are separate events and will be charged individually with Wootickets and Woocomerce.
Actually no, WooTickets does not support or understand recurring events.
So if a ticket is bought for the instance of the event on 3 May then they have effectively bought it for the whole series.
How you communicate that to your customers is a different challenge, but in principle that may work for you if I’m understanding things correctly.
OK, can you try something like this:
* Start Date: 02 May 2013 @ 0900
* End Date: 02 May 2013 @ 1800
* Recurring: Every Day ending on 04 May 2013Does that work for you?
