Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Robin W

    (@robin-w)

    thanks, that looks related to a ‘bulk’ edit – can you give me steps to reproduce please eg go to this, press that etc.

    Thread Starter Robin Labadie

    (@robin-labadie)

    Thanks for your time Robin (nice name! 😜).

    This error shows up in logs by simply adding a new blog post or editing one in my case.
    A blog post named “test” with default category and just “test” as post content also works.

    I shall note that this shows as a warning, not a critical error. So emergency level is quite low. I shall also say that I noticed this issue while debugging embedded YouTube videos not working anymore (shows 404 in logs and fails in WP), but it’s an issue on all websites from this whole server, not this specific website, so it is likely unrelated… My guess is Google blocks this server’s IP for some reason… Still investigating this.

    This website is quite fresh, i made it like 5 months ago, so chances for legacy issues are unlikely, though everything is always possible. It is also very light with 6 plugins only :

    • bbPress
    • bbp Style pack
    • Connect Matomo
    • OG — Better Share on Social Media
    • Social Sharing Block
    • WPMasterToolKit

    (I tried disabling the 3 last plugins from the list, error in logs remained the same. Other plugins made no sense to disable bbPress for this test).

    Theme is TwentyTwenty-Four.

    Hope you can easily reproduce and fix this little warning.

    All the best 🙂

    Dean Scott

    (@chrusion)

    My php-generated error log (not WP) is getting pounded by HUNDREDS of these undefined index _wpnonce errors, thus bloating the file.

    WP 6.6.2, edited TwentyTwenty-Four Theme, PHP 7.4, LiquidWeb Cloud VPS.

    Take this bit and multiply it 20 times over the course of a day to two. They’re ALL being generated by block editor usage (public viewing of posts/pages and admin editing), NOT BBPress (it was NOT being accessed during these timestamps) …

    It’s interesting that on line “3849” (not the actual line because of the use of “double” line returns creating a double spaced effect in the functions.php file, so actual line # is 7697) you have an empty( ) check on the function call, wp_verify_nonce( ), but not the nonce variable itself used in the function call.

    [08-Oct-2024 19:51:46 UTC] PHP Notice:  Undefined index: _wpnonce in /home/cnr/public_html/wp-content/plugins/bbp-style-pack/includes/functions.php on line 3849
    [08-Oct-2024 19:52:13 UTC] PHP Notice: Undefined index: _wpnonce in /home/cnr/public_html/wp-content/plugins/bbp-style-pack/includes/functions.php on line 3849
    [08-Oct-2024 19:52:13 UTC] PHP Notice: Undefined index: _wpnonce in /home/cnr/public_html/wp-content/plugins/bbp-style-pack/includes/functions.php on line 3849
    Plugin Author Robin W

    (@robin-w)

    the reason that nonce is called is because this function is called by an action ‘save post’, but only needed if we are doing a bulk save, hence it looks for the existence on the bulk save nonce, and does not execute unless present.

    I’ll add a further check to stop the warning in the next release.

    Thanks for raising.

    Thread Starter Robin Labadie

    (@robin-labadie)

    Thanks for your support @robin-w ! Looking forward for the fix. 🙂

    All the best 🙂

    Dean Scott

    (@chrusion)

    Excellent! Thanks for the prompt attention.

    Plugin Author Robin W

    (@robin-w)

    this should be fixed in 6.1.1 released a few hours ago

    Thread Starter Robin Labadie

    (@robin-labadie)

    Hi,

    Confirmed, no more error in logs!

    Thanks a lot for the quick patch, your rock!

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