HyperDB causes – Uncaught TypeError: Cannot read property ‘top

  • Resolved Pete

    (@angio)


    9 years, 9 months ago

    I’m using the latest version of query monitor as of today and have all plugins disabled and am using a default theme for testing.

    I get a query-monitor.js?ver=1473440905:67 Uncaught TypeError: Cannot read property 'top' of undefined error in my console at .addClass(qm.menu.top.classname)

    HyperDB is installed. When I remove db.php from the wp-content folder query monitor works. When HyperDB is enabled I see some HTML for query monitor on the page in dev tools.

    • This topic was modified 9 years, 9 months ago by Pete.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    9 years, 8 months ago

    This is most likely due to the fact that both Query Monitor and HyperDB use a wp-content/db.php file. This is a limitation of WordPress core and there’s currently no way that this can be resolved. Sorry!

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    9 years, 8 months ago

    That said, QM shouldn’t cause a JavaScript error, so I would try deactivating your other plugins one by one (and switch to one of the default themes) to see if the error goes away.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘HyperDB causes – Uncaught TypeError: Cannot read property ‘top’ is closed to new replies.