[Barry]

Awesome – looks like you’re on track!

There still seems to be some potential for it to cut the string after an element has opened but before it has closed, however it may be that isn’t a concern in your case.

At any rate, since we’ve moved into the realm of custom coding here and as it looks like you’re on your way to a solution I’ll go ahead and close out this topic – thanks again for posting 🙂

[Barry]

Hi J My,

I’m sorry to hear you are experiencing difficulties.

I see that you have a couple of Event Tickets Plus licenses: can you confirm if it is indeed Event Tickets Plus you are using, or are you still actively using the legacy WooCommerce Tickets plugin?

Additionally, could you share your system information?

Thanks!

[Barry]

OK – are you happy to progress this on your own in that case (or with the developer who created the theme)? I’m not sure quite how much further assistance we’ll be able to provide here.

[Barry]

Hi Ameet,

I just wanted to stop by and note that a preview release is available on the downloads page (to any one with a valid Community Events Tickets license) and that might provide you with some temporary relief until the next official release is ready.

Thanks!

[Barry]

In general we don’t go too far into custom coding tasks on the forums, but there are topics like this one that you may find interesting.

At this point it’s roughly a year old (there will naturally have been some changes in the codebase since then) and of course doesn’t present the complete answer, but it could still get you started on the right foot.

Cheers!

[Barry]

On a clean site, with no customizations and only a default, unmodified theme – do you find the same JS errors occur?

Could it be another plugin or your theme itself are conflicting?

[Barry]

Happy to help 🙂

[Barry]

Fantastic news!

I definitely recommend improving the built-in error messaging.

I agree 100% and will log this as a bug: the existing error messages were misleading, besides being unhelpful.

Apologies for the inconvenience and thanks for bearing with us through the troubleshooting process. I’ll go ahead and close this topic, but please don’t hesitate to create new ones as needed should anything else crop up.

[Barry]

You mean in the context of deleting events via the admin list?

If you hover over a given (recurring) event the link will either read as Trash if it is a single event or Trash Series if it is the base event (in which case, as the link implies, it will trash the entire series).

By default there is a column indicating if events are recurring, so you could quickly mouse over those and de-select any that are base events.

[Barry]

Hi Aindreas,

So suppose you set up a checkbox-style additional field, giving you an option like this in the event editor:

You could then add the following code to your theme’s functions.php file or indeed to a custom plugin:

function event_list_donation_marker( $cost, $post_id ) {
	// Only add the donation marker in list view
	if ( ! tribe_is_list_view() ) return $cost;

	$fields = tribe_get_custom_fields( $post_id );

	if ( ! empty( $fields['Donation'] ) && 'Yes' === $fields['Donation'] )
		$cost .= ' BY DONATION ';

	return $cost;
}

add_filter( 'tribe_get_cost', 'event_list_donation_marker', 100, 2 );

Does that help?

[Barry]

Hi Tim,

Unfortunately that is not supported at present.

The third party (and now unsupported) plugin Event Rocket does offer a means of doing this and you could potentially still use that, or use it as the basis of your own approach if it doesn’t quite fit your needs.

Another alternative – which we use on our own demo site – is simply using one of the many available redirect plugins to shift users instantly to the main events page, whenever they land on the homepage.

Beyond those options, it would really involve some custom development to implement this in the short term.

Remember also you can always vote for this on our UserVoice page 🙂

[Barry]

Hi @grantdayjames:

Thank you first of all for taking the time to report this issue. We take security issues very seriously and really appreciate you highlighting this.

I’ll discuss this with the team and once we’ve examined the problem in some more detail we will then take any further action that might be needed.

As a temporary measure, you could install and activate this plugin which should guard against most of the issues you described.

Thanks once again and of course we’ll keep you posted as things progress 🙂

[Barry]

My pleasure 🙂

[Barry]

Hi Allyson,

Please do create a fresh topic of your own and we’d be happy to look at the problem as it is in your specific case 🙂

Thanks!

[Barry]

Difficult to say; but as an alternative you could always revert to your backup and ‘manually’ delete expired events in batches.

The screen options pull-down tab lets you increase the number of events shown per page in the admin environment, so you could delete in batches of 100 (or even more than that), which while still slightly time consuming wouldn’t be too arduous a task – you could certainly make a big dent that way and you’d know that the delete operations were being done the “WordPress way” as opposed to directly modifying the database.

I’m afraid that not being able to replicate the issues you are describing, it’s difficult to provide much in the way of further insights.

[Author]

Posts