Conflict – get_current_screen

  • Resolved StarryMom

    (@starrymom)


    1 year, 11 months ago

    This involves another plugin, I contacted that author, and we both determined Jetpack is the issue.

    The function it’s talking about, in the other plugin, does exist. The only conflict it has is with Jetpack. 

    PHP Fatal error: Uncaught Error: Call to undefined function simple_download_counter_get_current_screen_pt() in /public_html/wp-content/plugins/simple-download-counter/inc/functions-admin.php:8
Stack trace:

0 /public_html/wp-includes/class-wp-hook.php(308): simple_download_counter_settings_flush_rewrite(Object(WP_Screen))

1 /public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)

2 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

3 /public_html/wp-admin/includes/class-wp-screen.php(424): do_action('current_screen', Object(WP_Screen))

4 /public_html/wp-admin/includes/screen.php(243): WP_Screen->set_current_screen()

5 /public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(505): set_current_screen('sync')

6 /public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(601): Automattic\Jetpack\Sync\Sender->get_items_to_send(Object(Automattic\Jetpack\Sync\Queue_Buffer), true)

7 /public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(462): Automattic\Jetpack\Sync\Sender->do_sync_for_queue(Object(Automattic\Jetpack\Sync\Queue))

8 /public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(404): Automattic\Jetpack\Sync\Sender->do_sync_and_set_delays(Object(Automattic\Jetpack\Sync\Queue))

9 /public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-actions.php(191): Automattic\Jetpack\Sync\Sender->do_dedicated_sync_and_exit()

10 /public_html/wp-includes/class-wp-hook.php(308): Automattic\Jetpack\Sync\Actions::add_dedicated_sync_sender_init('')

11 /public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)

12 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

13 /public_html/wp-settings.php(623): do_action('init')

14 /public_html/wp-config.php(97): require_once('/…')

15 /public_html/wp-load.php(50): require_once('/…')

16 /public_html/wp-blog-header.php(13): require_once('/…')

17 /public_html/index.php(17): require('/…')

18 {main}

thrown in /public_html/wp-content/plugins/simple-download-counter/inc/functions-admin.php on line 8

    Best I can figure out is both are calling get_current_screen and that’s where the conflict resides. How can we resolve this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @starrymom

    Could you please post your site URL here so that we can have a look?

    If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.

    Thanks!

    Thread Starter StarryMom

    (@starrymom)

    https://onestarrynight.com

    However it doesn’t show on the frontend, just the error logs. Which fill up extremely quickly so I try not to keep Jetpack activated for long. I have it activated at the moment since you asked.

    Hello again

    https://onestarrynight.com

    However it doesn’t show on the frontend, just the error logs. Which fill up extremely quickly so I try not to keep Jetpack activated for long. I have it activated at the moment since you asked.

    Thank you for your feedback. In this particular case, I recommend that the plugin’s developer perhaps review our developer documentation. There may be a better way for their plugin to do what it needs to do that avoids this sort of conflict.

    On the other hand, if they feel this is a bug, they can also report the issue to our developers through our developer page here: https://developer.jetpack.com/ (there is a link in the right sidebar to Report a bug).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict – get_current_screen’ is closed to new replies.