Support » Plugin: SpeakOut! Email Petitions » Errors after upgrading to WP5.3

  • Resolved goranbla

    (@goranbla)


    I’ve been having the same issue as described in this post, using WP5.3.

    After activating the plugin, I get errors in the dashboard (thrown out right after the body tag):
    Notice: Undefined index: dk_speakout in /var/www/wordpress/wp-admin/includes/plugin.php on line 1392
    and
    Warning: count(): Parameter must be an array or an object that implements Countable in /var/www/wordpress/wp-admin/includes/plugin.php on line 1392

    In addition, when activating the plugin (on the “Installed Plugins” page), I see an error box (rendered as a div with class error) with the content:
    The plugin generated 411 characters of unexpected output during activation. If you notice β€œheaders already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    When opening a page with a petition shortcode on it, the following 4 errors are thrown and shown:
    Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.) in /var/www/wordpress/wp-includes/functions.php on line 4903

    Notice: wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (0) for the number of arguments passed (1). Please see Debugging in WordPress for more information. (This message was added in version 4.8.3.) in /var/www/wordpress/wp-includes/functions.php on line 4903

    Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.) in /var/www/wordpress/wp-includes/functions.php on line 4903

    Notice: wpdb::prepare was called incorrectly. The query does not contain the correct number of placeholders (0) for the number of arguments passed (1). Please see Debugging in WordPress for more information. (This message was added in version 4.8.3.) in /var/www/wordpress/wp-includes/functions.php on line 4903

    The petition itself is shown and seems to work, though… This goes for the admin interface as well, I can see the submenu, can use the plugin, and all, but get these error messages.
    Again, when deactivating this (and only this) plugin, all works fine.

    I’m running this on a test / experiment site (with full access to the server), so can do just about anything to help with figuring this out. (I’m an experienced developer and know my way around a server; not a WP/PHP developer, though πŸ˜…)

    I’m running WP5.3 (latest at the time of writing) on Ubuntu Linux (18.04.3), with these plugins (all up to date versions):

    • Code Snippets
    • Contact Form 7
    • SpeakOut! Email Petitions (obviously πŸ™ˆ)
Viewing 15 replies - 1 through 15 (of 22 total)
  • Just noticed the same wpdb::prepare was called incorrectly notices are “spat out” when opening an existing petition for editing in the admin interface.

    The first two mentioned errors (well, notice and warning, if we want to be technical 😊) are shown on any admin page, not just the speakout pages.
    Which makes sense, just thought I’d mention it anyway.

    I’m also getting this error. I’m not seeking support just confirming the error is present.

    Plugin Author 123host

    (@123host)

    Thanks for this. I was notified of your earlier “me too” reply and am a bit puzzled by it being deleted. Knowing that this is happening for more than one person is absolutely important to a developer – at this point I don’t care about configurations…I just want to know about it. Having a single thread where multiple people can be included is also helpful. Strange rules for some reason…sigh…

    Can you do something for me (because I can’t recreate this). Disable all your plugins and see if it still happens.

    If that fixes it, enable the plugins one by one and see which causes the error.

    If disabling all plugins doesn’t help, switch to the twentytwenty theme and see if that solves it.

    Please report back what you find. You can also contact me via https://speakup.123host.net.au if you would like me to take a closer look.

    Hi, I disabled all plugins and switched to the twenty-twenty theme with no luck. The errors are still displayed when I activate the plugin speakout.

    My project is in a development environment on a live server,

    Regards,
    Fish911

    • This reply was modified 3 months, 1 week ago by fish911.
    Plugin Author 123host

    (@123host)

    @fish911 you will get a wrist slap from the forum moderators for offering login details πŸ˜›

    I’d like to discuss other ideas you can try. Can you get in touch via https://speakout.123host.com.au

    Sorry, ouch! Yes, I will contact you via https://speakout.123host.com.au right now.

    Plugin Author 123host

    (@123host)

    FOUND IT! Thanks so much @fish911 – couldn’t have done it without you.

    FWIW this wasn’t affecting the plugin itself, only the menus in the dashboard.

    Pushing version 1.18.2 shortly.

    • This reply was modified 3 months, 1 week ago by 123host.

    Yeah, I’m running this on a test server and offered a bit more help than just doing things myself… and got a wrist slap πŸ˜‚ that’s why the reply was removed ☺️
    (that and the “me too”, it seems the moderators rather see individual posts, not sure why)

    anyway, glad to see you’ve found it. I’m guessing I don’t need to go through the same procedure as @fish911 now πŸ˜‡
    Although, I did see the wpdb::prepare notices on pages with a petition shortcode, not just the dashboard.

    I’ll be glad to upgrade to the new version and try it out. (and report, obviously)

    thanks for the quick reply and work πŸ€“

    Plugin Author 123host

    (@123host)

    The attitude of the moderators is that a post belongs to the person who created it, not to the author. So each person should open their own thread to avoid the OP getting all the “me too” notifications. It makes a little sense, but from an authors point of view it isn’t ideal, so many replies to have to do. But them’s the rules.

    “From all reports” πŸ˜‰ in @fish911 test site there were no wpdb::prepare notices.

    I look forward to hearing how you go with 1.18.2.

    yeah, rules are rules… they’re not there just for “us”, so… πŸ˜…

    Anyway, tried upgrading the plugin, but now got some other errors… πŸ˜•

    A lot of these (5, which is the exact number of plugins I’ve added to my system):
    Notice: add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be an integer representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.) in /var/www/wordpress/wp-includes/functions.php on line 4903

    Still seeing the wpdb::prepare notices as well… both on the dashboard (when editing a petition) as well as on a test page.

    I’ve sent you a message through your site.

    Tried the new (twenty-twenty) theme as well and don’t see a difference.

    Plugin Author 123host

    (@123host)

    OK…the “5” also happens to be the number of submenu items. Putting quotes around a value fixed it for @fish911 – i have received your email. Will follow up.

    the β€œ5” also happens to be the number of submenu items

    πŸ˜… *d’oh*

    Plugin Author 123host

    (@123host)

    I have just updated a couple of site where I test to 1.18.2 and I am also seeing any errors. Stick with me…we will solve this.

    It seems that on some sites it likes the quotes and not on others…this is frustrating

    we will solve this

    I have no doubt, really… πŸ˜‰
    Let me know if there’s anything I can do πŸ‘

Viewing 15 replies - 1 through 15 (of 22 total)
  • You must be logged in to reply to this topic.