[Jonathan Goldford]

Thanks for getting back to us George. We switched to the Twenty Fifteen theme and deactivated all plugins except for the Events Calendar ones, and unfortunately, no luck.

We’ve now found two separate issues that relate to submitting the form with errors. Could these be related at all? The other issue was posted on https://theeventscalendar.com/support/forums/topic/bug-event-start-date-end-date-reset-when-errors-returned/ and has yet to be fixed.

Let me know if there are any other steps you’d like us to try.

Jonathan

[Jonathan Goldford]

Thanks for getting back to me Josh. Do you have any timetable of when this fix will be implemented within the plugin itself?

[Jonathan Goldford]

Hi Josh,

Since this was taking a while to tackle we went ahead and took a shot at it. We were able to fix this by making the following change.

On line 20 of /src/views/community/modules/datepickers.php we changed the code from:

if ( get_post() ) {

To:

$existing_post = get_post();
if ( $existing_post && !isset( $existing_post->EventStartDate ) && !isset( $existing_post->EventEndDate ) ) {

We overrode the template by duplicating the file into theme/tribe-events/community/modules/datepickers.php, but of course we’d love this to be in the plugin in case any substantial updates are made.

Can you confirm that this code looks good on your end and works how you all would expect? We did test it, but you guys would likely know test cases we don’t.

Thanks.

Jonathan

[Jonathan Goldford]

Thanks Josh. Hopefully you all will have a chance to tackle the bug soon.

[Jonathan Goldford]

Hi Josh,

Can you update us on the status of this ticket?

Thanks a ton.

Jonathan

[Jonathan Goldford]

We’re also seeing this issue. Looking forward to having this fixed as soon as possible.

[Jonathan Goldford]

Thanks for the quick reply! I have updated the three plugins on the staging site and have reproduced the issue. I have narrowed it down to a conflict with a template override we made to organizer.php in order to hide a few fields. You can take a look at the overrides made here: http://pastebin.com/regzH5sg

Essentially, we just want to remove the following elements from Organizers:
– Use Saved Organizer
– Email obfusciation text
– Add another organizer link

I would imagine that we’d be able to do this by completely removing our organizers.php override and instead overriding the fields with organizer-fields.php instead, but my organizer-fields.php override doesn’t seem to be working. I removed “<?php tribe_community_events_organizer_select_menu( $event ); ?>”, but the organizer dropdown field was still there. I also threw some plain text in the file, but that did not appear on the page either.

Am I going about this the right way? What’s the best way to make this customization?

Thanks for your help!

[Jonathan Goldford]

Thanks a ton Josh. That code was very helpful. We adjusted it slightly to work only with The Events Calendar. Here is the code in case anyone else needs it:

<?php
/**
 * Disable the Yoast SEO admin list columns when looking at The Events Calendar events.
 */
function wi_disable_yoast_seo_columns_on_event_list() {
	if ( !is_admin() || ( defined( 'DOING_AJAX' ) && DOING_AJAX ) || !isset( $_REQUEST['post_type'] ) ) {
		return false;
	}

	global $pagenow;
	$post_type = esc_attr( $_REQUEST['post_type'] );
	
	// Remove the Yoast SEO columns only if we're on the admin event list view
	if ( $pagenow === 'edit.php' && $post_type === 'tribe_events' ) {
		add_filter( 'wpseo_use_page_analysis', '__return_false' );
	}
}
add_action( 'init', 'wi_disable_yoast_seo_columns_on_event_list' );

Take care.

Jonathan

[Jonathan Goldford]

Thanks Geoff. It looks like the database table are already storing in UTF-8, so I don’t think that plugin is what we need.

Hopefully this will help someone else, but we decided to go a fix that removes invalid characters on output for both the content and the description in the feed. Here is the code we used:

/**
 * Adjust the RSS feed description and content to remove invalid UTF-8 characters.
 *
 * Invalid characters were causing issues with the RSS feed pulling into the calendar because people were copying 
 * into the Community Events system with invalid UTF-8 characters. This causes errors within the RSS feed that kept it from working correctly when trying to pull events to our other sites.
 */
add_filter( 'the_content_feed', 'wi_remove_invalid_characters', 10, 2 );
add_filter( 'the_excerpt_rss', 'wi_remove_invalid_characters' );
function wi_remove_invalid_characters( $content, $feed_type = '' ){

	if( $feed_type == 'rss2' ){
		return mb_convert_encoding( $content, 'UTF-8', 'UTF-8'); //Removes invalid characters
	}

	return $content;
}

Thanks again for the help.

Jonathan

[Jonathan Goldford]

Thanks Geoff. It looks like the database table are already storing in UTF-8, so I don’t think that plugin is what we need.

Hopefully, this will help someone else, but we decided to go a fix that removes invalid characters on output for both the content and the description in the feed. Here is the code we used:

/**
 * Adjust the RSS feed description and content to remove invalid UTF-8 characters.
 *
 * Invalid characters were causing issues with the RSS feed pulling into the calendar because people were copying 
 * into the Community Events system with invalid UTF-8 characters. This causes errors within the RSS feed that kept it from working correctly when trying to pull events to our other sites.
 */
add_filter( 'the_content_feed', 'wi_remove_invalid_characters', 10, 2 );
add_filter( 'the_excerpt_rss', 'wi_remove_invalid_characters' );
function wi_remove_invalid_characters( $content, $feed_type = '' ){

	if( $feed_type == 'rss2' ){
		return mb_convert_encoding( $content, 'UTF-8', 'UTF-8'); //Removes invalid characters
	}

	return $content;
}

[Jonathan Goldford]

Thanks Geoff, but that would still be a ton of regular manual work. Wouldn’t it make some sense to look at removing those characters on output of the rss feed via code? That way there wouldn’t be any manual work involved at all.

Jonathan

[Jonathan Goldford]

Thanks Geoff. The invalid characters are in the post content itself which is pulled from the Event Description field within Community Events. Unfortunately, we can’t do them manually because they aren’t actually visible within the WordPress editor, and there are multiple events a day, so the amount of time would be fairly significant, even if we used some sort of search and replace plugin.

Any other suggestions?

[Jonathan Goldford]

Thanks Brian. I was actually able to make it work by using a new action called ‘tribe_community_event_created’. I’ve updated my gist at https://gist.github.com/jg314/5299d64d073c6d3e0a67 to include the new code for anyone else that needs it. Thanks again for the help.

[Jonathan Goldford]

Thanks Geoff. I’ll go ahead and start a new thread.

[Jonathan Goldford]

We are having a very similar issue in that we were actually directing users to a new page once they submitted an event. Here is the code we were using that is no longer working: https://gist.github.com/jg314/5299d64d073c6d3e0a67

Can you provide us some direction on how to fix this, since redirecting users to a new page was critical for tracking goals via Google Analytics.

Thank you.

[Author]

Posts