[Geoff B.]

Good evening Mario,

Thank you for the info.

That allowed me to run some tests.

I believe there is a problematic CSS rule in place

.event-custom-fields input {
width: 98%;
}

Try adding the following CSS rule to your style.css file or in your Custom CSS metabox:

.event-custom-fields input {
width: auto !important;
}

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good evening M.,

That is both disappointing and surprising.
I just double checked and tested the snippet.

On my end it works perfectly.
So I am wondering if there is not a theme conflict at play.

Could you please send me a copy of the latest version of your WordPress theme / child theme via a link to a .zip file link (stored Dropbox or Google Drive) so that I can run some tests on my end ? I recommend a private reply for that purpose.

Please ensure you are using the latest files as found on your actual website (including that snippet). This way I will get access to any updates or customizations you might have made.

Additionally, if you have not already done so, I would highly recommend updating to Event Tickets Plus 4.4.5 as it provides better integration with WooCommerce 3.

Finally, do you know if there is a caching system in place on your site ?

Hang in there!

Geoff B.

[Geoff B.]

This reply is private.

[Geoff B.]

Good evening David and welcome back!

First off, I would like to apologize for the delay answering.
We are currently experiencing a higher level of requests than usual.

Please rest assured that we are working hard at correcting this situation.
We appreciate your patience while we try to normalize things.

Thank you for reaching out to us.
I would love to help you with this topic.

You could apply the following snippet in the functions.php file of your theme (without the PHP tag at the top): https://gist.github.com/elimn/36b24ada494337b5dad7

Let me know if that helps.

Have a great day!

Geoff B.

 

[Geoff B.]

Good evening Susan and welcome back!

First off, I would like to apologize for the delay answering.
We are currently experiencing a higher level of requests than usual.

Please rest assured that we are working hard at correcting this situation.
We appreciate your patience while we try to normalize things.

Thank you for reaching out to us.
I would love to help you with this topic.

You can apply the following snippet in the functions.php file of your theme (without the PHP tag at the top): https://gist.github.com/GeoffEW/b440feef873af841d023c0bf0839e93f

Normally, that should hide the word “free” on your site.

As a side note, it looks like your the Events Calendar Pro version is in need of an update.

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good afternoon James,

I am super stoked that this worked for you!

You are welcome back in our support forums any time 🙂

For now, I am going to close this thread.

Have a great week!

Geoff B.

[Geoff B.]

Good afternoon Marco and welcome back!

Thank you for reaching out to us.
I would love to help you with this topic.

If I understand correctly the documentation available, currently Event Tickets Plus does not support any:
– WPML
– Recurring events

That is officially accurate.

I am purposely saying officially because in both cases, there are things that can still be done, but there is no complete solution available.

 

Event Tickets Plus vs WPML

This feature is scheduled to be release later this year. Initially we planned for spring, but there has been some pushback. So I do not have a date at this point unfortunately.

In the meantime, you could get it to partially work, but this is unsupported.

To achieve that, you will need:

1. WooCommerce multilingual
2. Some manual intervention

After creating the ticket AND saving the event, head over to WPML > Support > Troubleshooting page.

Once you are there, you should see several cleanup buttons. I would recommend:

1. Clearing WPML cache
2. Using the button that forces language assignment to items (which is what is creating the issue). This can also be accomplished by deactivating and reactivating WPML.

Your ticket will now magically appear.

The only downside is that the tickets you create in other languages are not really translations of the initial ticket. They are completely independent new tickets.

Event Tickets Plus vs Recurring Events

We are currently completely re-designing our recurring events engine to support many new features including full Event Tickets Plus support.

Here again, I do not have a release date to offer alas. But stay tuned!

At the time of writing, you can still use Event Tickets Plus  with recurring events, but there is a major caveat: the tickets created are exactly the same for all events.

In other words, these tickets are shared between all events.

 

Best regards,

Geoff B.

[Geoff B.]

 

Good evening Tibor and welcome to the Events Calendar Support forum!

Thank you for reaching out to us.
I would love to answer you different points and questions.

I am very confused by the way the WPML support works for your plugin.

I would highly recommend reading the following which clarifies what we do and what we don’t support for the moment: https://theeventscalendar.com/knowledgebase/wpml-support/

Personally, I don’t get the point why a ticket has to be tied to a Page/Event. I run a festival, one event only -> no need to have multiple events. I would really appreciate if I could create tickets as WooCommerce products only and not tied to a specific Page/Event.

I see your point and how that does not meet your specific situation’s needs. Thankfully, this approach does work for a lot our users.

Since this could be a cool feature to have and I am pretty sure there are others with similar needs to yours out there, you can suggest it in our User Voice forum. That way other customers can vote for it!

After creating the Page and a ticket, a WooCommerce product is also created, however, it’s URL points to the created Page (which it is linked to) instead.

To make a long story short, our plugins are not yet fully compatible with Event Tickets Plus or Event Tickets (as per the first article shared).

 

This feature is scheduled to be release later this year. Initially we planned for spring, but there might be some pushback.

In the meantime, you could get it to partially work, but this is unsupported.

To achieve that, you will need:

1. WooCommerce multilingual
2. Some manual intervention

After creating the ticket AND saving the event, head over to WPML > Support > Troubleshooting page.

Once you are there, you should see several cleanup buttons. I would recommend:

1. Clearing WPML cache
2. Using the button that forces language assignment to items (which is what is creating the issue). This can also be accomplished by deactivating and reactivating WPML.

Your ticket will now magically appear.

The only downside is that the tickets you create in other languages are not really translations of the initial ticket. They are completely independent new tickets.

The subject line of the e-mail can’t be translated – string not found by WPML. Please, check that one out.

That is very possible, provided the above.

For now, your best shot will be to do a template customization for that purpose (until the compatibility is ready).

You might want to read our Themer’s guide to get a sense of how that works.

Summa summarum, I am quite frustrated by the means the whole translation works now. It creates inconsistency in my website. Overall, I would be glad if I could use the WooCommerce product template in all language mutations. I would expect to be able to create tickets as sole WooCommerce products without the need of creating a Page, as well.

I certainly understand how that could be frustrating. Hopefully the workaround above could be of some assistance until we release true WPML compatibility and it goes through the full dev cycle.

That still would not address your second expectation, but hopefully your feature request idea will gain some fast traction!

As a side note, some of our customers have been successful integrating Event Tickets Plus with Polylang (which is not officially supported), but I thought that would be something you would be interested in.

 

Best regards,

Geoff B.

[Geoff B.]

Good afternoon William and welcome to the Events Calendar Support forum!

Thank you for reaching out to us.

We are sorry to hear about the error messages you have been dealing with. Yikes!
I would love to help you with this topic.

We apologize for the inconvenience caused by this glitch.
We have identified the cause of the error and a fix should be released very shortly.

The good news is that you will be contacted as soon as a fix is available.
Thank you for your patience as we see this through.

In the meantime, you can see the details of the fix here: https://github.com/moderntribe/products-extensions/pull/37/files

Best regards,
Geoff B.

[Geoff B.]

Good afternoon Christopher,

I am super stoked that this is working for you!

You are welcome back in our support forums any time 🙂

For now, I am going to close this thread.

Have a great week!

Geoff B.

[Geoff B.]

This reply is private.

[Geoff B.]

This reply is private.

[Geoff B.]

This reply is private.

[Geoff B.]

Good evening Danielle,

I believe I have found the culprit.

It is a rule in your Divi CSS.

.entry-content tr td, body.et-pb-preview #main-content .container tr td {
padding: 6px 24px;
border-top: 1px solid #eee;
}

As you can see, this forces a horizontal padding of 24px, hence the exagerated size.

Try adding the following CSS rule to your style.css file or in your Custom CSS metabox:

.tribe-mini-calendar td, .tribe-mini-calendar th {
padding: 0 7px!important;
}

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good evening Michelle,

I ran a few tests and here is an idea that might help.

Try adding the following CSS rule to your style.css file or in your Custom CSS metabox:

#tribe-bar-form.tribe-bar-collapse #tribe-bar-views {
z-index: 1;
}

Let me know how that goes.

Best regards,
Geoff B.

[Author]

Posts