Hey Kelly,

Unfortunately the Events Calendar Pro plugin is a known conflict. When developing WordPress plugins it’s recommended to give your functions unique identifiers to avoid conflicts with other plugins functions – In our case we use ‘sp_’ (for Simple:Press).

Events Calendar Pro have a function ‘sp_get_option’, which we also have and have had for some time (if not from the start, not sure) and this causes the conflict.

It’s not as simple as us renaming our function, not just because all of our functions begin with ‘sp_’ but more because changing it would disturb the installs of many of our existing users.

I thought a while back Events Calendar Pro had changed theirs, but if you have the latest version I guess they haven’t. Your best bet is to see what they say.

Ike – thanks for the quick response.  I just got a response from The Events Calendar, which seems to resolve the problem (based on limited testing; both plugins are active with no apparent issues).

They advised to remove the function you mentioned; of course there is no guarantee of future issues but here is their reply in case others are reading this:

George wrote:

        Hey Kelly,

Sorry to hear about this! This is be arising from the fact that we have a function called sp_get_option inside The Events Calendar at line 134 or so in this file: the-events-calendar/src/functions/template-tags/deprecated.php

The function looks like this:

if ( ! function_exists( ‘sp_get_option’ ) ) {
       /**
        * @deprecated
        *
        * @param        $optionName
        * @param string $default
        *
        * @return mixed
        */
        function sp_get_option( $optionName, $default = ” ) {
                _deprecated_function( __FUNCTION__, ‘2.0’, ‘tribe_get_option()’ );

                return tribe_get_option( $optionName, $default );
        }
}

This is a deprecated function, so you can literally just remove that code block entirely with no ill effect.

I’m sorry about this issue, but hope this solution helps!

— George

This is most interesting and I did not know they had done this. In effect it means that if the SP plugin had loaded BEfORE the Events Calendar plugin all would have been well. Probably by deactivating both and then reactivating in the correct order would overcome the issue.

I will remember this as it does crop up every now and then but you are the first to share with us the response from the calendar team. Thanks for that.