Plugin is triggering “wp_enqueue_script was called incorrectly”

  • Hey, the plugin seems to trigger “wp_enqueue_script was called incorrectly” since a few weeks maybe. I now deactivated it, I’m not quite sure, but I’ve also had database problems over the last weeks, and it could be SiteSpeaker plugin is doing its part on that. Will there be an update in the next time to fix this?

    Used it for a few months now, never had problems, so it seems the new version of WordPress caused this or maybe the fact that I changed to another database system instead of MySQL.

    If others also have this problem, would be great to notify me in this thread, because I really liked the plugin, but if it caused any problems, that would be a reason to not use it anymore. One of the problems was constant “error establishing database connections”, I don’t know if SiteSpeaker caused this, but since QueryMonitor nailed the problem down to its source which was SiteSpeaker, I think it could have been the problem.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author ken107

    (@ken107)

    Hi there,

    Sorry for the late reply. I’ve just tested with WordPress 6.1.1 and the plugin is working normally as before. I updated the plugin to indicate compatibility with the latest WP version on the plugin store.

    This plugin does not access any database directly; those errors are probably coming from your WP installation. When you’re in the Settings page, the plugin calls some APIs to retrieve the list of voices and that’s it. Are you able to enter the Settings / SiteSpeaker Widget page?

    Thread Starter Bastbra

    (@comicschau)

    Hi, thanks a lot of your answer.

    It seems the plugin did not cause the database errors, that seems to be something different – although I still don’t know what.

    I will send you more information on the case with the problem as soon as I am able to, at the time I deactivated it. With Query Monitor I was able to track this down, so I thought this would be the issue I was searching for, but even if it certainly is an issue, it does not seem to be that problematic to cause more. Thanks also for your clarification!

    I will try to search more, get more details of this issue (maybe this is just something with Query Monitor and not really a problem), and hopefully find the actual problem that I am searching for right now.

    Best regards and thanks for your effort so far!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin is triggering “wp_enqueue_script was called incorrectly”’ is closed to new replies.