Conflict with WP Log Viewer

  • Resolved TheRealMikeD

    (@therealmiked)


    4 years, 2 months ago

    I noticed that, after upgrading to version 14.9 of Yoast SEO, I was not seeing any settings on the settings screens (e.g. /wp-admin/admin.php?page=wpseo_dashboard#top#features). Just a save button with nothing to save.

    The Chrome DevTools console shows a few JS errors:

    Uncaught TypeError: Class extends value undefined is not a constructor or null
    at Object.<anonymous> (components-1490.js:24)
    at n (components-1490.js:1)
    at Object.<anonymous> (components-1490.js:1)
    at n (components-1490.js:1)
    at Object.<anonymous> (components-1490.js:24)
    at n (components-1490.js:1)
    at components-1490.js:1
    at components-1490.js:1
    in /wp-content/plugins/wordpress-seo/js/dist/components-1490.js

    Uncaught TypeError: Cannot read property ‘StyledSection’ of undefined
    at Object.<anonymous> (settings-1490.js:1)
    at f (commons-1490.js:1)
    at Object.<anonymous> (settings-1490.js:1)
    at f (commons-1490.js:1)
    at Object.<anonymous> (settings-1490.js:1)
    at f (commons-1490.js:1)
    at Object.<anonymous> (settings-1490.js:1)
    at f (commons-1490.js:1)
    at Object.<anonymous> (settings-1490.js:1)
    at f (commons-1490.js:1)
    in /wp-content/plugins/wordpress-seo/js/dist/settings-1490.js

    I loaded this page in an incognito window to ensure that there was no interference from a Chrome extension.

    Then, I tried deactivating my other plugins. I finally determined the conflict to be with WP Log Viewer (https://www.ads-software.com/plugins/wp-log-viewer/). It would seem that that plugin is affecting the way the JS loads for Yoast SEO.

    While this issue is not, strictly speaking, a flaw in the Yoast SEO plugin, I thought that you would like to know about it, and perhaps take some preventative measures to stop it from happening. I will be filing a similar support issue with the makers of WP Log Viewer.

    Using WP 5.5.1, Yoast 14.9, WP Log Viewer 1.2.1.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support devnihil

    (@devnihil)

    @therealmiked It looks like the WP Log Viewer plugin hasn’t been updated for over 3 years, and is only tested for compatibility with WordPress up to version 4.8.14 so the issue is likely due to the code for the plugin being not kept up to date.

    However, if you wish to, you’re welcome to submit a bug report. We’re actively using the bug tracking on our GitHub repository so you’re able to create a new issue for our developers at https://github.com/Yoast/wordpress-seo/issues/new. You will need an account to create a new issue. If this is your first bug report, please check out: https://kb.yoast.com/kb/how-to-write-a-good-bug-report/.

    Thread Starter TheRealMikeD

    (@therealmiked)

    Thanks for the response, @devnihil.

    It doesn’t seem terribly urgent, given the state of WP Log Viewer’s development. I might file a bug report if I find a few free minutes. I really just wanted to make sure you all were aware of it in case something similar happens to another user.

    Probably the best solution is for me to A) file a bug report with WP Log Viewer; and B) look for another, more updated, plugin which provides the same functionality as WP Log Viewer, since that one looks like it may have been abandoned. Too bad. I find it super-useful.

    Cheers!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with WP Log Viewer’ is closed to new replies.