• Resolved mealto

    (@mealto)


    As I was migrating to a new server, one site has been throwing up errors on every page load. I was able to track it down to Sportspress conflicting with Beaver Builder (I think).

    I understand that when all other plugins are deactivated, Sportspress alone does not throw this error. But I can say the same thing with Beaver Builder. It doesn’t throw this error enabled on its own either.

    Here is the exact issue that I found. I know each company has their own reasons for coding things a certain way, but this is not the first time that I found SP conflicting with BB / Beaver Themer. Hopefully, there is a simple fix for this one.

    Any help would be greatly appreciated! Any ideas on how we can rectify this?

    wp-includes/functions.php:5167
    is_tax()
    wp-content/plugins/sportspress/includes/sp-template-hooks.php:95
    sportspress_gettext()
    wp-includes/class-wp-hook.php:287
    apply_filters(‘gettext’)
    wp-includes/l10n.php:187
    translate()
    wp-includes/l10n.php:254
    __()
    wp-content/plugins/bb-theme-builder/classes/class-fl-page-data.php:83
    FLPageData::init_defaults()
    wp-content/plugins/bb-theme-builder/classes/class-fl-page-data.php:66
    FLPageData::init()
    wp-content/plugins/bb-theme-builder/classes/class-fl-page-data.php:492
    FLThemeBuilderLoader::load_files()
    wp-content/plugins/bb-theme-builder/classes/class-fl-theme-builder-loader.php:70
    FLThemeBuilderLoader::load()
    wp-includes/class-wp-hook.php:287
    do_action(‘plugins_loaded’)
    wp-settings.php:403

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Roch

    (@rochesterj)

    Hi there!

    Thanks for your message. Indeed, quite often we can’t provide support for conflcits, but let’s see what we can do for this one.

    It isn’t clear for me what the error message is, though. Here I can see the files, code lines but not the actual error/warning/notice.

    BTW, is it a error or just a notice?

    Thanks!

    Thread Starter mealto

    (@mealto)

    Thank you! The error was in the title. Let me paste it below:

    is_tax was called incorrectly

    I have opened a ticket with Beaver Builder devs too. Will post back once I hear back for them as well. Appreciate it!

    • This reply was modified 3 years, 11 months ago by mealto.
    Plugin Contributor Roch

    (@rochesterj)

    Hi there!

    Please post the entire error here. We can’t see from that if it’s an error, a notice, a warning.

    Notices and warnings should be harmless and you should still be able to usue all functions just fine.

    Thanks!

    Thread Starter mealto

    (@mealto)

    Here is one line from the WP Debug log:

    PHP Notice: is_tax was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/domain.com/htdocs/wp-includes/functions.php on line 5167

    Plugin Contributor Savvas

    (@savvasha)

    Hi @mealto ,

    As you can understand, it is not easy to reproduce the issue you have, so it is quite difficult to propose a solution.

    At your first post, it seems that SportsPress part of conflict is the following line:
    elseif ( ! current_theme_supports( 'sportspress' ) && $untranslated_text == 'Archives' && is_tax( 'sp_venue' ) ): from wp-content/plugins/sportspress/includes/sp-template-hooks.php. From here someone can suspect the is_tax( 'sp_venue' ) code, but as you can see here https://developer.wordpress.org/reference/functions/is_tax/ the function is_tax() is called correctly from SportsPress. Maybe the Beaver Themer manipulates somehow the custom taxonomies? I really don’t know. If this function was not called correctly, there was going to have conflicts with other plugins too, not only with Beaver Themer.

    Please come in contact with Beaver developers and return some feedback here.

    Thanks,
    Savvas

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘is_tax was called incorrectly; conflict with Beaver Builder’ is closed to new replies.