[Geoff B.]

Good afternoon Alan and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the struggles you have been experiencing while attempting to upgrade our the Events Calendar Pro add-on. I would love to help you with this topic.

Normally, this process is seamless. I am not sure why the installer is stopping on your site because the folder already exists.

Another workaround that might solve this for good (for the next update) is to:

1. Deactivate Pro and Delete it completely
2. Install a fresh version from the Downloads section (using the .zip file).

I have a hunch that a brand spanking new install should clear this type of issue.

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

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

Thank you for reaching out to us.

We are sorry to hear that it’s no longer possible to select venues or organizers after the latest upgrade. I would love to help you with this topic.

There are a couple of things I would recommend to try to get things working with your setup:

1. I notice that you are using an older version of PHP. I strongly advise getting at least PHP 5.4+ in there, as many features of WordPress related plugins are not that great otherwise.
2. Your max PHP execution time is set to 0. Try increasing it to 300

Secondly, I am not sure if you have any template customization in your child theme (/tribe-events/ folder). But if you do, they might need updating. Try disabling them temporarily to see if that helps or better, simply revert to the parent Customizr theme.

Ideally all these tests would be better performed in a test / staging environment.

To buy you some time, you might want to downgrade Community Events to 4.3.2 : https://theeventscalendar.com/knowledgebase/downgrading-plugin-past-version/

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good afternoon Hovig and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the links not displaying on your site.
I would love to help you with this topic.

What is going on is that there is CSS rule interfering

a {color: hsla(0,0%,62%,0);}

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

.tribe-events-sub-nav a {color: rgb(170,51,57);}

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good afternoon Faiza and welcome to the Events Calendar forum!

 

Thank you for your interest in our products. It’s truly appreciated.

However, please note that we do not offer support for our free plugin in this premium add-ons forum.

But, the good news is that you are still welcome to consult this forum to your liking and browse it for solutions, snippets and tutorials.

If you don’t mind, in the future could you please post your support questions here: https://wordpress.org/support/plugin/the-events-calendar ?

With that in mind, it looks like there could be 1 or 2 things at play:

1. You might not be using pretty permalinks on your site (%postname)
2. Some of these URLs might have been generated on events that had no title when initially published and somehow, made it to your Google Site Map without getting refreshed afterwards.

In any case, I will let you continue this conversation over in our .org forums.

Best regards,

Geoff B.

[Geoff B.]

Good morning Hans-Gerd,

Awesome!

A maintenance release is due this week.
I will mark this thread as “pending fix” so that you get contacted once this issue is ironed out.

Best regards,

Geoff B.

[Geoff B.]

Good morning Russell,

I am super stoked that this worked out 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 evening Scott,

First of all, I want to apologize for the delay answering.
As it turns out, I absolutely had to be out of the office yesterday.

I realize the timing of this could not have been worst.

Secondly, I am truly sorry to hear that you missed the window of opportunity you had to fix this issue. I wish downgrading to the previous version would have done the trick (it usually does).

That being said, thank you for running these additional thorough tests.

I will gladly refund your Community Tickets license.

But before we do this (since this is your suggestion), there is indeed one last thing that would be worth a shot.

Full disclosure, we did have bumpdown error messages a few versions back, but it was not related to Community Tickets. It happened on servers that had certain specific SSL / https configuration that led to mixed content.

Since you do not seem to be using https (that I know of), I doubt this is the case.

I would like to offer to try to reproduce this on my installation.

Could you please send me a copy of the latest version of your wp-content folder 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.

My theory is that this might actually be related to the server type you are using (5.5.9-1ubuntu4.20).

In any case, we truly apologize for this very puzzling inconvenience.

Have a good weekend,

Geoff B.

[Geoff B.]

Good evening Shadi,

I am sorry for the delay in response (I realize the timing could not be worst).
I had to be out of the office yesterday.

The news I have is that this is now a priority one ticket.
I doubt it will be ready for this week’s maintenance release, but should clearly make it for the following one.

I wish I had a better answer for you, but for now it’s the best one I have.

In the meantime, if you would like to explore the idea to convert all of the tickets to actual products (as opposed to virtual ones), I the following snippet could serve as inspiration: https://gist.github.com/jesseeproductions/5768685acc4cd48cdd81

This is meant to change the default behaviour of the catalog visibility of tickets, but you should easily be able to  make tickets non-virtual.

As a side note, you actually do not need the Calendar plugin (installed or activated) to use the tickets. It is totally possible to use tickets in any post type of your choice (as established under Events -> Settings -> Tickets).

Let me know if that helps.

Have a great day!

Geoff B.

[Geoff B.]

Good evening Yulia,

Thank you for your answer.
I do have some good news on my end.

After some pretty lengthy investigation, it looks like this issue is actually server dependent.
This might explain why you are not able to reproduce it on other environments.

We apologize for the inconvenience caused by this glitch.
We are actively working on a fix for this.

Unfortunately, I cannot commit to a release date for a fix at this point.

But you will be contacted as soon as there is one.

Thank you for your patience as we see this through.

Best regards,

Geoff B.

[Geoff B.]

Good evening Paul,

Thank you for the example.

I went ahead and looked at your site and somehow, there is no trace of the previously suggested CSS rules ?

In case this is an issue related to format they are again with some tweaks.

Try adding them to your style.css file or in your Custom CSS metabox:

@media only screen and (max-width: 600px) {

table.tribe-events-tickets tr .woocommerce {
width: 100% !important;
}

table.tribe-events-tickets tr .tickets_name {
width: 100% !important;
}

table.tribe-events-tickets tr .tickets_price {
width: 100% !important;
}

table.tribe-events-tickets tr .tickets_description {
width: 100% !important;
}
}

That should fix the portrait issues.

As for the landscape part, try

@media only screen and (max-width: 600px) and (orientation: landscape) {
table.tribe-events-tickets tr td {
padding: 15px 6px;
}
}

Let me know if that helps.

Have a great day!

Geoff B.

[Geoff B.]

Good evening Steph,

Thank you for writing back.

Unfortunately, our policy does not allow us to log in to clients websites to change anything for several reasons, including liability.

At best, we can take a look (which I did) to see if we can’t spot anything obvious.

What is going on is that your theme or one of the plugins on your site is forcing a resize of the image.

As a result, instead of using the basic image URL (i.e.: https://i0.wp.com/www.rookieraceline.com/wp-content/uploads/2017/01/DiceChallengerace.jpg), it uses the following URL https://i0.wp.com/www.rookieraceline.com/wp-content/uploads/2017/01/DiceChallengerace.jpg?resize=125%2C125&ssl=1

The only way to know for sure what the cause of this is to go through our testing for conflicts procedure (preferably in a staging/dev environment or local install of your WordPress website) and let us know what you find out.

Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.

But, before you do that, there are 2 things I would advise:

1. Make a backup of your database
2. Consider activating a “Maintenance Page” plugin if you are doing this on your live site (to minimize impact on your visitors)

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

Good evening Simone,

Thank you for your answer.

I am glad you were able to make some progress.

Let’s try to address the other issues.

Number 2: You can simply change this using a template customization.

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

The view file that needs to be modified is /wp-content/plugins/event-tickets/src/views/tickets/RSVP.php (line 23).

If you change RSVP directly in the plugin file, it will be overwritten during the next plugin upgrade.

If, however, you make a copy of that file and place it in the /tribe-events/event-tickets/src/views/tickets/ of your WordPress theme, it will resist plugin upgrades.

For number 1: You need to paste the code starting at “add action” and end at the last closing  }.

Perhaps, this version is clearer: https://gist.github.com/cliffordp/13078d8bd9ba7879dacbdfaba81ea120

Let me know how that goes.

Best regards,
Geoff B.

[Geoff B.]

This reply is private.

[Geoff B.]

Good evening Hans-Gerd,

Awesome! I can confirm that for now 2 workarounds exist:

1. The one Andras gave to Marcus and yourself (although not super clean, it’s the easiest)
2. Updating the pot file from sources and then updating the po file from the updated pot file

Either way, we will release this in our next Maintenance release due next week.

Have a good weekend,

Geoff B.

[Geoff B.]

Good evening Tomonori,

I am sorry the link did not work.
As you have guessed, the proper way to do this is to use translation files.

Since it looks like you are pressed for time, there are 2 very fast ways to do this:

1. Use and adapt the code snippet found at the bottom of this page: https://theeventscalendar.com/knowledgebase/change-the-wording-of-any-bit-of-text-or-string/ . Use that code in the functions.php file of your WordPress theme
2. You could simply override the strings in question directly in our plugins file. The complete list of the view files in our Themer’s guide .

For example, to override Community Event’s front-end submission file (which looks like the screenshot you have sent me), the view files are all located in /wp-content/plugins/the-events-calendar-community-events/src/views/

Let me know how that goes.

Best regards,
Geoff B.

[Author]

Posts