[Barry]

Hi Hans-Gerd,

We appreciate you flagging this!

The most recent Community Events release introduced a number of features but wasn’t intended to fix all outstanding bugs. On reviewing this other topic you had created about the same problem, it looks like the translation has been added to relief is in sight and Andras will be able to help with any further questions you might have.

With that in mind, I will now close this topic.

[Barry]

Hi Mieke,

Can you confirm you are using the plugin provided in the following knowledgebase article?

theeventscalendar.com/knowledgebase/fast-forward-list-widget-to-next-upcoming-event

This doesn’t actually require you to modify your theme’s functions.php file in any way, it’s a bit more “plug and play” than that. If you are using code from elsewhere, can you link me to it so I can assess it?

Thanks!

[Barry]

Hi Miquel,

My client can not create recurring events translated by incompatibility errors.

Can you clarify the problem you’re seeing here so I can ensure it’s been correctly logged?

When I create a recurring event and translate it to another language, so long as I follow the steps recommended for normal events it appears to work as expected.

I can, for instance, visit a specific instance of the recurring event (taking place on 2017-07-01 as an example) and successfully switch to the other language on the same date.

Are you finding this isn’t the case for you? Or, is the problem something quite different from this?

I’d love to learn more so we can better guide you or identify and log any bug reports that might be needed 🙂

[Barry]

Hi Dmitry,

Thanks for flagging this!

I can certainly see the same thing if I log in as an editor or administrator, but not for other tiers of user.

Can you confirm the roles of the users you are experiencing this with? If they are custom roles of any kind, can you if possible detail the capabilities they have been granted?

Thanks!

[Barry]

Hi Ben,

Sorry to hear you’ve hit up against the bumpers, here.

Unfortunately this seems to be the result of a bug. To that end, I’ve added this forum topic to our internal bug report and we’ll do our best to update you once we’ve had an opportunity to work on this.

Our apologies for any inconvenience in the meantime.

[Barry]

Excellent, happy to hear it 🙂

[Barry]

So it certainly seems like things aren’t working in your case, I’m not sure why but it could be a conflict of some kind.

• Can you share your system information via a private reply? theeventscalendar.com/knowledgebase/sharing-sys-info
• Can you try running through our recommending conflict testing steps? theeventscalendar.com/knowledgebase/testing-for-conflicts

Simply because this isn’t a problem we can replicate (nor so far as I’m aware is it something many other users are experiencing or reporting on the forums) it does seem that the above troubleshooting steps would be worthwhile.

Can you give them a shot?

[Barry]

Hi Greg,

I’m afraid Geoff isn’t available right now (though hopefully will be back soon!).

Given, however, the amount of work you’ve done behind the scenes to get us to a stable and working point with these 7 sites, I’m really worried about applying a general release and breaking things.

All we can really advise in these situations is that you test in a duplicate staging site and/or make a backup so you can restore things if the update doesn’t pan out as expected.

Lots of users have already updated successfully and they’ve been able to take advantage of numerous fixes and improvements – but I do appreciate your own site may be a special case and you may rightly wish to proceed with caution.

We have the same error with CPMR that we in fact experienced with another site (a Not for profit pro licence, clean install, didn’t work out of the box, tribe refused to help)

In general, we do not provide support for sites covered by a non-profit license here in the premium forums which is why we may have declined to help previously.

The problem you described is certainly odd – but given it is unrelated to the primary issue being discussed in this topic can I ask that you create a new forum topic?

Thanks!

[Barry]

Happy to hear it, @copephotos.

Derek: can you confirm if this specific problem is resolved in your case, too?

[Barry]

The pre-release/beta period for Community Events 4.5 has now concluded. All further questions relating to Community Events should be posted in the regular forum 🙂

Our thanks to everyone who participated!

[Barry]

Hi everyone,

There have indeed been some teething problems with this service, but we’ve been working hard at correcting them and we hope our latest releases will supply many of you with relief from this specific issue (where manually running import jobs succeeded but failed for the same sources when running automatically/in the “background”).

Please do update your plugins and let me know if the latest fix has helped.

Thanks :-

[Barry]

Glad it improved things.

I also want to share something else that is possible as of the latest release. If you add the following snippet, ideally to a custom plugin, it will remove the attendee column (which indicates the percentage of tickets sold):

add_filter( 'tribe_tickets_supported_admin_columns', '__return_empty_array' );

If you need that column to be present then of course this would not be the best way to go, but if you don’t then it will stop a potentially large number of queries from running when building up the admin list table.

[Barry]

Excellent, thanks! I can now replicate 🙂

Unfortunately, there is a conflict between your theme’s CSS (specifically, I believe, from “Swift Framework” which is a part of Dante) and our own plugin. I have a fairly simple solution, however. Please create a new file (you may also need to create the mu-plugins directory if it doesn’t already exist) here:

wp-content/mu-plugins/swift-tec-compatibility.php

Add the following code to that file:

<?php
function remove_swift_css_from_event_editor() {
	wp_dequeue_style( 'page-builder-css' );
}

add_action( 'admin_head', 'remove_swift_css_from_event_editor', 5 );

If that doesn’t work however I’d encourage you to work further with the theme author: ideally, they would not add their CSS to admin screens other than those they are responsible for (there’s no real need for them to add Javascript and CSS to the event editor screen, as an example – in fact it causes the problem you have been experiencing).

That said, hopefully the above solution works for you 🙂

Good luck!

[Barry]

This reply is private.

[Barry]

Excellent 🙂

[Author]

Posts