Forum Replies Created
-
Posts
-
By the way, you guys are pretty responsive with your support for a smaller team with many customers (I know i’m not your only one, sadly, would love the attention … lol)
Cool… there are three or more threads with this issue so you might want to hit up the others with similar issues.
For now, I’ve had to write a complete separate form for adding tickets 🙁
I’ve also found the ‘order’ in which you activate plugins is important (not just yours, but others). I’m assuming this is because of the order in which scripts get loaded on the page also. (aka who gets’s priority). So the main reason for the site was to generate income, but that plugin is conflicting, as are stylesheets, so I look forward to the new versions, and hopefully we haven’t customised so far by then with other products/plugins we can implement them.
There are two issues here:
1) you are handling something that should be handled by woocommerce using ‘groups’ or a ‘mall’ type feature.
2) that option shouldn’t even be showing there if I don’t have split payments enabled.Ironically the functionality that IS hidden because of split payments being off is the ability for a seller to absorb the fees or not and other option. I think this is all back the front… the two hidden fields should be visible _always_ and the paypal item should not be visible if split payments isn’t.
–> This is about to become an architectural review really… 😉
3) The other issue is most ticketing companies hold the money until the event runs so they can refund tickets should the event not run (or such). This means that either 1) a bank account or 2) a credit account (paypal/stripe/etc) needs to be entered to be paid out at the end.
This needs to be modularised (like you have with ticket type, but pleeeeeeease make it easier to implement than tickets #sigh)… so that the events calendar ‘DETECTS’ the payment plugins installed and their features (aka split peyments for stripe/paypal), and also allows for services like NAB Transact (aussie bank) to take the details and store a token (like stripe does) for BSB and bank account details for direct debt without storing sensitive information.
It’s on the community events end-user page, there are two tabs, events and payment info.
This is far more simple than that. You round percentages to 1 decimal point in your code.
Two would be more reasonable.
The ability to charge this as part of the fee or not is also hidden if I don’t have split payments enabled, but not sure why the ability to absorb the fees isn’t always on? (or have an admin option to turn on).
It should be the sellers choice to whether they absorb fees or not, not a global setting.
External Ticket Source:
Yes I do this with custom fields at the moment, but it’s clunky and you can’t import ticket links from facebook that way also. (would love custom field support for imports – another request for another day)
1) would love to be able to specify the external ticket link that produces a button to click ‘Buy Tickets’, aka a link with a nice button.
2) would love to create a ticket with a price, pointing to ticket link (which allows you to display pricing of the event)The reason for the button, is the same as my issue with current ‘website’ if the url is long, then it wraps or overlaps other text in the box, so a button makes it neat, and you can have a tooltip come up with the link if you want UX.
—
Donation:
I think it would be good to offer both options:
1) the ability to enter the amount
2) the ability to default that amountWe have had requests for this at the ticket level. So you select 2 adult, 1 child and enter a donation amount, then go to the cart.
Now you are right you put put the ‘upsell’ there, but that Is also the issue in some cases where people see it as an after the fact upsell, rather than a conscious choice… people will side either way on that one.
add_action( 'pre_get_posts', 'tribe_post_date_ordering', 51 ); function tribe_post_date_ordering( $query ) { if ( $query->tribe_is_multi_posttype) { remove_filter( 'posts_fields', array( 'TribeEventsQuery', 'multi_type_posts_fields' ) ); $query->set( 'order', 'ASC' ); } }Needed “ASC” otherwise events way in the last list first. I need the next event to list first, so just reversed the order.
Used this, but also need to make sure events disappear when their ‘end-date’ has been reached… the query needs the ‘end-date’ column added to the query to do this, or a subquery condition… where is the best hook to do that?
we did test them in development, and in test… they did different things in production.
Out of five rebuilds 4 yielded different bugs within the community events and community tickets plugins. Each rebuild (in dev) gave different errors #shookhead #confused Also badly written upgrade scripts initialise new plugin differently to fresh install… this is common with wordpress plugins… quite often your plugins just didn’t render anything on the page due to conflicts, sometimes half a page, then sometimes the full page with no styles and no javascript functionality…
The ORDER in which plugins are initialised also matters… different sequences delivers different results (not just your plugins but others also)
This is mainly due to clashes with Redux framework IMHO. (one big one is jQuery date picker plugin – several posts on this forum regarding that conflict) – this kills the categories selector on community events… I found 3+ posts about this lately on this forum.
it’s too easy for other classes to be ‘eventForm’ and override key layout items, also for javascript to manipulate that.
I guess you’ve got to realise that most theme makers grab a wordpress framework (in my case the themer used Redux) which carelessly (and I’ve reported it to them also) uses generic classes also, and to add to that uses a minifier that reduces script variables to a,b,c… in the global scope #OMG.
At least you guys had the brains to use scoped javascript (even after minification)… #thanks so you’re most of the way there…
It would also be great if you limited the scope of your plugins also (aka to slugs that are /event + /shop and grab the others from shop config) so that it helps our site run faster outside the event pages… which would help to reduce some of the bazillion style and javascript files on every request (that most aren’t needed sadly).
also would love to see the /community slug be optionally removed from community events, and just use /events as they are just another author really (or contributor)… Already added that to the UV page.
I’ll write up a series of tickets in a couple of weeks when I can build some videos to show the issues. Right now we’re a week into launch and we’re bleeding because of ‘our’ choice to apply a minor update.
We also need to deal with local issues, such as sellers who some are tax-registered and some that are not gst-registered as with the community tickets the SELLER dictates if tax on tickets is charged, where the tax on fees stays the same for all people. We have to implment an extra field in ‘Organiser’ to put ABN (tax id in Aust) and a second field ‘GST Status’ => ‘Not Registered (no gst), Registered (gst)’.
The issues in the 2016 theme are:
1) The Community Events and Community Tickets plugins (especially the tickets one) are highly volitile.
If you went to the website christianevents.net.au, you’d see that neither plugin shows pages, however both are active.
Both list and add for community events where working, then we simply disabled and reenabled both plugins as we couldn’t get the ticket area to work as it had a javascript error (for all four rebuilds, but the last)
This site was to launch last week (friday). We upgraded the plugins and now the whole submission system is down. We can’t get it to work, so we’re rebuilding the entire site. With ONLY your plugins and WordPress the error is the same. HOWEVER, on the FIFTH rebuild now it works. I’m baffled to why.
We’ve blown a week of sales at a key time of year where we have only one more week to get end of year school clients, so now we’ve lost one of those weeks and for a business launching that already had delays, this I guess explains my stressy posts of late (sorry about that)… I just need this to work as advertised, and the community plugins are not complete, especially in the theme department. (out of the box that is).
I’m building this site for a client that is a proof of concept for other clients, and because of bugs we now have two systems running side by side, so we’re now about to cut our losses with TEC if this doesn’t work by tomorrow. Our devs are now working on a backup system in case this doesn’t work. After 5 rebuilds, finally I’ve got the site working as a skeleton, but I still have to add a series of woocommerce plugins and customisations, so fingers crossed.
christianevents.net.au was working, we did an advertising launch, then we did the minor upgrade and the whole community area is now not even rendering. more than ten times we’ve deactivated, reactived those plugins and others… nothing… that site is dead with new leads leaving by the minute. It’s a major embarassment. A minor upgrade and we’re off air, effectively. Pretty much dove that business into the ground, as the advertising money. But that’s on us, we trusted your updates (major fail on wordpress)…
Some of the list of obvious changes needed asap.
1. jQuery plugin conflicts
2. No cancel button on CET page.
3. ‘List’ of events link disappears when you’re adding an item.
4. Tickets area breaks in a thousand ways5. Tickets are created without a woocommerce category
6. orders don’t automatically complete (big problem) and script given doesn’t work consistently.…
Most caching plugins allow you to ignore urls… just put the scanning url into the exceptions of your cache plugin.
