[George]

Hey @Robin,

Thanks for reaching out!

Caching plugins in general can often cause issues like the one you describe here. This is quite a bummer, but there is one thing you can try to be able to use both plugins without issue:

• Check out the W3 Total Cache settings and see if there are settings related to “script minification” or “stylesheet minification”. If so, deactivate/disable everything minification-related that you can.

If this does not help, then unfortunately the plugins may be inherently incompatible on your site 🙁

Let me know what you find!

— George

[George]

Hey Marian,

Really sorry about the trouble here! I checked out our email inbox and found an email from you on Februrary 1.

The next day, on February 2, our support engineer Hunter responded to you over email with the following email:

Hi Marian,

Check out our knowledgebase article for details on transferring licenses (https://theeventscalendar.com/knowledgebase/moving-your-license-keys/). If you have any further questions, don’t hesitate to get in touch or post on the PRO Forum.

Cheers,
Hunter

1. Did you get this reply from Hunter?

2. If not, then I would recommend following the advice in his reply and reading that Knowledgebase article he linked to.

— George

[George]

Hey @bkozlowski,

The answer here would actually be “yes” to both of the questions you posed. To clarify, yes, the first case you gave is true because of the truth of the second case you gave.

We have not actively developed and/or tested integration with WooSubscriptions & WooMemberships at this time, and so our tickets or incompatible with the “subscription” product type.

Tickets can only be the default products or the “simple product” type within WooCommerce that it provides by default; there are no other support product types at this time.

Sorry to disappoint about this!

Cheers,
George

[George]

Hey Mark,

No extra info can be collected at this time unless you were to write a bunch of custom code to do so. We will be releasing features sometime this year, hopefully, that will enable the collection of extra info. But there is nothing at this time.

---

As for security, our plugins themselves are secure and WooCommerce itself, which handles the eCommerce aspects of all of this, is secure as well. WooCommerce stores some customer data, namely:
• Name
• Address
• Phone number if entered
• Email address

No payment data is stored on your site or in your database, ever. Users have to use PayPal to make their purchase, or other payment gateways if you add them, like Stripe. These payment processors themselves handle all payment-related data.

I hope this information helps!

Cheers,
George

[George]

Hey @Alvaro,

The bug is happening when there’s no element on the page called .entry-footer. We’ve tried this when logged in, when not-logged-in, when logged in as a low level like subscriber, etc.

We cannot recreate this specific bug with events, however we can reproduce it in some locations on a site with the Twenty Sixteen theme.

This is an odd bug and I unfortunately do not have any immediate action I can recommend at this time, except for one suggestion that might help:

I wrote a modified version of Twenty Sixteen’s javascript file where this error is coming from. The modified version is here → https://git.io/vgc7M

I would recommend navigating to this file in your copy of Twenty Sixteen:

/twenty-sixteen/js/functions.js

Replace that file with entire contents of the link I shared above, save the file, and then see if anything improves with the error on your page….

I’m sorry about the persistence of this bug, @Alvaro.

I hope this helps!

Cheers,
George

[George]

Hey @Kadi,

Thanks for your follow-up questions. Just to be reiterate a point I mentioned earlier, we cannot help with plugin customization-related questions, and so I will unfortunately have to close this thread soon. Please see the “Product support” section of this page for more information → http://theeventscalendar.com/terms

---

As for your follow-up questions here in this thread:

1. Can the content in the “additional fields” be broken up so that one filed can go to the top of the form and another one can go at the end?

Yes, but this could potentially lead to bugs so please tread lightly while you make these sorts of edits! To do this, just head to the file being called for a specific “section” of field content. So when you see this bit of code:

tribe_get_template_part( 'community/modules/taxonomy' );

If you would like to make more granular edits to the taxonomy section’s actual content, then just head to the file in views/community/modules/taxonomy.php and then edit this file’s contents directly.

2. Is there a way to shorten the drop downs for the beginning/end times so that they fit on one line (they seem to be taking up way more space then needed)?

This sounds like the result of some CSS and style weirdness arising from the styles on your site. YES there are ways to fix this, but you will have to use developer tools to find the CSS causing this spacing and write CSS to fix this.

Also can I rename the “ADDITIONAL FIELDS” label? I tried using the directions for the venue & organizer fields in the functions php file but it didn’t help & I can’t find directions anywhere else.

Yes. This would require CSS customizing which I mentioned above, but try and be a bit more helpful here, here’s some CSS you could add to hide that label:


#event_custom #event-meta .tribe_sectionheader {
display: none !important;
}

We cannot help with customizations or any further questions related to customizations. If you have other questions that fall within the “Product support” section of this page please let me know and I’ll try and help!

Sorry to enforce a policy this way, @Kadi. I do sincerely wish you the best of luck with your site.

If you have no further questions here, let me know and I will close up this thread.

Sincerely,
George

[George]

I hope we see this soon, too, Paul! Stay tuned to “Changelogs” in plugin updates or to http://theeventscalendar.com/blog for release notes – if this feature arrives, it’ll be noted in both locations.

I’ll close this thread for now, but feel free to open a new thread any time if other issues arise.

Cheers!
George

[George]

Hey @mark,

At this time we unfortunately have no “pay to upload” features in any of our plugins 🙁

Sorry to disappoint! Let me know if there’s anything else I can try to help with.

Sincerely,
George

[George]

Hey @Neal,

I’m really sorry to hear about this loss of custom work 🙁

There is indeed a way to prevent this from happening, which is WordPress’s excellent “Child Theme” feature → https://codex.wordpress.org/Child_Themes

If you make a child theme of the parent “Divi” theme, and then add your customizations into this child theme, then you can update the Divi theme without affecting the code within the child theme.

Check out the article above for more information on how child themes work, how to make one, etc.

I really hope this helps! Let me know if that’s the case and/or if there’s anything else I can help with.

Sincerely,
George

[George]

Hey Ingrid,

Thanks for reaching out!

This is unfortunately not possible at this time without some extensive code customization 🙁

I’m sorry to disappoint – please let me know if there’s anything else I can help with!

Cheers,
George

[George]

Hey Marcel!

Thanks for reaching out, and for the link to the existing version of the “scheme” you are trying to recreate here.

Our plugins unfortunately do not offer a “scheme” layout or feature that looks like the one you are trying to build 🙁

I’m sorry about this!

It would indeed require a large amount of custom coding.

I don’t know of any alternative plugins to suggest that do have these features, but if hiring someone is something you’re interested in, we have a list of customizers here that might be helpful → http://m.tri.be/18k1

We have no affiliation with those folks, they’re just some well-respected names in the community that we’ve compiled.

Cheers!
George

[George]

Hey @Linda,

I’m really sorry to hear about these issues with your site.

To be clear, what’s happening here is not that our plugin files themselves are the “source” of the attack or something.

The attackers are trying to access our plugin files.

While I do not know why this is the case, both of the files in this error report–and all source files within our plugin–are protected by checks that kill execution immediately if they’re loaded outside of WordPress. These are trying to load the files outside of WordPress, so our code will die immediately when requested in this way.

This is unfortunately something that it seems you still need to work with your host to resolve–really sorry about the issues you’re facing and I wish you the best of luck with this problem!

Please let me know if this information is helpful and/or if there’s anything else I can help with.

Sincerely,
George

[George]

Hey Juan,

Thanks for reaching out!

Yes, to use Community Tickets you would need all of the following plugins to be installed and activated on your site:

• WooCommerce
• Event Tickets
• Event Tickets Plus
• The Events Calendar
• The Events Calendar: Community Events

And then finally:
• The Events Calendar: Community Tickets

I hope this helps!

— George

[George]

Hey Mina,

Thanks for reaching out!

This use-case is actually not specifically supported by our tickets. I’m sorry about this!

At this time, there is no “shared stock” feature like you describe. You have to set a quantity/stock for each ticket option. We’re not fans of social engineering! 🙂 The problem is just that, at this time, the “shared stock” aspect of this feature is something we are still ironing out within our code because each eCommerce platform that we want to support (e.g. WooCommerce, Easy Digital Downloads, etc.) handles “stock” management in slightly different ways.

It’s a trickier problem to solve than it might sound, but this “shared stock” / “global stock” feature is:

• literally one of the most-requested features of all time for our plugins

• something we’re about 90% done with implementing! 😀

We’re hoping to have this released in the plugins before summer is upon us, though this is a rough estimate and one that we’d only be able to meet if all goes to plan.

Sorry for the disappointing news here; but I wanted to make it clear that we share your (and many other customers’) desires for this feature to be realized and are working on it.

Please let me know if there’s anything else I can help with!

— George

[George]

Hey Augustin,

Thanks for reaching out!

While having 5 tickets with different names and prices per ticket is indeed possible, there is not a way to automatically-generate this information 🙁

I’m sorry to disappoint! Please let me know if there’s anything else I can help with.

Cheers,
George

[Author]

Posts