slug conflict

Hi, Pedro. Did you try changing the slug setting within the Events -> Settings page? You can set the slug to whatever you want:
https://gyazo.com/035ccb06ec18f7e62615c79b3116eb4c

Here is documentation for The Events Calendar settings page for your reference:
https://theeventscalendar.com/knowledgebase/wp-admin-settings-overview/

Let me know if that does the trick.

Mike

Hi, Tribalmike

Yes, I tried it. It keeps showing the same warning with every new different slug name (https://prntscr.com/l7v7e0).

The message appears in every search with results.

Any new suggestion?

Thanks

Interesting… Is this causing any issues on the front-end of the site or is it only this warning that keeps popping up?

Mike

Sounds like another plugin could be creating a conflict. Please ensure that your plugins are up to date. If no functionality is being impacted, you can hide the message with this snippet in your functions.php:

/* tribe remove slug conflict notice */
function tribe_remove_slug_conflict_notice ( ) {

	if ( !class_exists('Tribe__Admin__Notice__Archive_Slug_Conflict') ) return;
	remove_action( 'admin_init', array( Tribe__Admin__Notice__Archive_Slug_Conflict::instance(), 'maybe_add_admin_notice' ) );
}

add_action ( 'init', 'tribe_remove_slug_conflict_notice' );

All our plugins are up to date.

It seems to be conflicting with mDocs. With all plugins disabled and twenty seventeen theme, it still occurs.

It only shows when using the search feature inside any kind of page or post, with words that would produce results. For example, with “test” (https://prntscr.com/l9j69x), waste, energy, fire. All words that we have within the site content.

Haven’t found yet functionality impact. The frontend search seems to be working ok.

Any suggestion to solve it? I’m in contact with mDocs developer, who ask for some clue.

I’ll try the code.

Thanks

If its not impacting the front end performance, then I’d just try to hide the message with the snippet Ed shared above. Let us know how things work out for you.

Mike

Hello, Mike
I’ve tried the snippet, hadding it to functions.php, but it’s not hiding the message.
Can you please verify it?
Thanks