Community Events / Tickets

[Chris]

There needs to be more focus on ‘finishing’ these plugins… they are half done, especially around theme collisions and alike.

Could you _please_ use unique references to tribe classes and styles so that ANY theme will not collide… what about prefixing ALL styles and id’s with ‘tribe_’ or ‘tec_’ or ‘tec_cet_’ for community events tickets. The current state of theming for Community Events is poor.

I have used event tickets, and it works perfectly, then community tickets add event, well pretty much everyone’s suffering through that experience, ignoring the defplate, not using page title styles, communittickets doesn’t even work half the time, (sometimes I get the heading ‘Add Tickets’, other times, just nothing. Pretty much every theme in this universe breaks the jQuery selector plugin for categories… t
This code should never have been released. It’s half baked. Please rename all of the classes and ids as a starting point, this seems to be (from the support threads here another places) the main issue… clashing versions of jquery… #ohboy…

So pretty much our site at christianevents.net.au isn’t able to list ‘ticketed events’ at the moment… community tickets is a writeoff… even on my dev environment the ONLY theme it works with out of the 40 I’ve tested (including one that supports tec) is 2016 base theme, and no-one on earth uses that theme.

I’m going to have to re-write this plugin just to make it work. Well worth the dollars I spent #not… it’s never worked, but now I’m actually needing to use it… wasted my money… but now stuck on a deadline debugging and rewriting two plugins I paid (A LOT) for.

I’d be the biggest fans of yours if the quality of code was consistant, if the styles where professionally written (with non-clashing unique prefixes)… Here goes my entire week fixing YOUR issues, instead of selling tickets to events, I’ll be telling people to wait for a custom solution, and hopefully your next updates of other plugins doesn’t break them also.

For the fourth time I’m about to rebuild wordpress from scratch starting with your plugins while I watch my subscriptions expire before I will even get to launch the site… if I can’t fix it by then, well it’ might be time to walk away.

Please finish these plugins, they need the other 20% of work done. #bleadingtears

[Chris]

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 ways

5. Tickets are created without a woocommerce category
6. orders don’t automatically complete (big problem) and script given doesn’t work consistently.

…

• This reply was modified 9 years, 5 months ago by Chris.

[Chris]

Hello… is this thing on?

[Geoff]

Hi Chris,

Welcome back and nice to see you again!

In reading through your feedback, it certainly does sound like you have bumped into some theme and plugin conflicts while using both Community Events and Tickets.

I do have good news in that we are in the process of updating the design interface for Community Events and hope to have that in one of our upcoming major feature releases — it won’t be in the very next one (4.4) but it is on our roadmap. And, when it does release, it will use a lot more unique IDs and classes that sound like would benefit you as far as running into the styling and jQuery conflicts you mentioned.

As far as the other items you mention, these sound like legitimate feature requests and we’d be happy to consider them. For example, adding a WooCommerce category to a ticket is possible after the ticket has been created, but it would be a feature enhancement to make that happen in the ticket creation process. It’s a good idea, and it (along with the others) would be awesome to see added to our feature request forum.

Some of the other things you mention sound like possible bugs:

• Tickets area breaks in a thousand ways
• orders don’t automatically complete (big problem) and script given doesn’t work consistently.
• ‘List’ of events link disappears when you’re adding an item.

…but it’s honestly hard to (1) troubleshoot them without additional details and (2) to troubleshoot them all together in the same thread. Would you be willing to open separate threads for each issue? That will allow us to focus on each issue separately and get multiple folks on the team here to look at them.

And, when you do open the threads, it would be awesome if you could re-confirm whether the issue(s) persist in the default WordPress Twenty Sixteen theme. I realize you mentioned having tested it in your first reply, but doing so again in each thread will help isolate whether each issue is related to a specific theme conflict or something in the core plugin files.

For what it’s worth, I know that dealing with theme conflicts are frustrating and I deal with them myself in the projects I work on as well. I do want to respectfully remind you at the same time that conflicts are often a two-way street and, while we are unable to guarantee compatibility with each and every third-party theme and plugin, we do make sure that our plugins work with default WordPress components because those are the closest examples available for a baseline of how something should work right out of the box. That doesn’t mean we will not attempt to build compatibility for other third-party components, but even then, that often require changes by both us and the third party component.

Let me know if you’re willing to open those threads for us and I’ll be sure to flag them for the team right away.

Thanks,
Geoff

[Chris]

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)…

[Chris]

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)’.

[Geoff]

Hi Chris,

Thanks for following up and I appreciate the additional details. We’ll definitely look forward to the tickets so we can address the issues you’re facing directly on a one-to-one basis.

One comment you made is a little striking to me and deserves a retort:

Right now we’re a week into launch and we’re bleeding because of ‘our’ choice to apply a minor update.

Just to confirm: please make sure you are testing your updates in a development environment before applying them to a live production website. Whether an update is considered “minor” or “major” does not change the best practice for any WordPress, theme or plugin to test those updates in a safe environment. While we test all of our releases extensively, it is no replacement for testing in your own environment because it is impossible for us to test against all the free, commercial and custom themes.

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.

If you find that the functionality of the plugins did indeed work in a previous version, then please do revert the plugins to the last working versions. Again, it’s key to test any and all updates before fully implementing them. However, it sounds as though you were able to get things working well with previous releases and reverting to those versions sounds like a good temporary solution while we work together on the issues you will be reporting.

We’re looking forward to digging into this with you!

Geoff

[Chris]

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.

• This reply was modified 9 years, 5 months ago by Chris.
• This reply was modified 9 years, 5 months ago by Chris.

[Geoff]

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.

Oh, that’s really good to know. Sounds like a conflict with the Redux Framework is a good possibility. In fact, if you haven’t opened a support ticket with them for help isolating its scripts from appearing where the calendar is, then that would another route to pursue in addition to the tickets you open with us here.

If it’s ok with you, I would like to close this thread since we’ll be moving to the individual threads you will be creating for each isolated issue you plan on reporting. Let me know if that is ok or if you have any additional comments to add here before we move on to those threads.

Thanks,
Geoff

[Chris]

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.

[Geoff]

Hey Chris!

Man, I love this comment:

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)

We do care a heck of a lot about our customers and doing the best we can do right by each and eery person, yourself included. You’re absolutely right that we’re running a small, but tight ship around here. Even though that prevents us from doing everything we get asked to do, it also allows us to get more personal when it comes to support and get to the heart of things. I’m stoked to hear this feedback from you.

You can be assured that we’ll get to your threads. Our team is hard at work fielding threads this very moment and throughout the rest of the day heading into the weekend. We’ll see you in those threads and I’m looking forward to getting these issues and concerns resolved together with you. Thanks for your partnership and cooperation!

Cheers,
Geoff

[Author]

Posts