That’s a weird error to encounter – it’s usually the case of an invalid nonce key in the ajax request.
Does that happen all the time? On all post types or only pages?
Hi @edward_plainview,
This does appear to happen on all broadcasted post types and on multiple sites here on our network. I see it on my local install as well.
The only item I’m finding in the console is:
XHRPOST
https://www.xxx.com/wp-admin/admin-ajax.php
[HTTP/2 403 Forbidden 504ms]
We just upgraded Broadcast (and NextGEN Gallery) yesterday. Hadn’t noticed the issue before this, though.
Also found this locally:
{“key”:”9f1f4a9bcafb9d33d19e3131c20d0417″,”type”:”deprecated”,”message”:”sprintf(): Passing null to parameter #1 ($format) of type string is deprecated”,”file”:”wp-content\/plugins\/threewp-broadcast\/src\/sdk\/form2\/form.php”,”line”:559,”stack”:[“sprintf()”,”plainview\s\f\form::sprintf()”,”plainview\s\f\i\hidden->value()”,”plainview\s\f\i\hidden->use_post_value()”,”plainview\s\f\form->use_post_value()”,”plainview\s\f\form->post()”,”plainview\s\w\f\form->post()”,”plainview\s\f\form->is_posting()”,”threewp_broadcast\ThreeWP_Broadcast->wp_ajax_broadcast_post_action_form()”,”do_action(‘wp_ajax_broadcast_post_action_form’)”],”component”:”Plugin: threewp-broadcast”}
Can also confirm that rolling back to Broadcast 50.03 resolves the issue locally.
In 50.04 I added nonce checking for the settings forms, but that should not have affected the ajaxing.
Which version of PHP are you using?
Does rolling back to .03 solve the problem on live also?
I’m testing PHP 8.1.9x on local, and we’re running 7.4.3x on production.
I can try rolling back on production to see what happens, haven’t tried that one yet.
Yes, rolling back also works on production.
Tested unlinking a post with PHP 8.1.10. Worked just fine. Also finding unlinked children works fine.
I’m not sure what the problem could be: the line with the is_posting() function is called in src / traits / post actions.php, line 690. By that time all of the nonce and access checks are finished.
So I don’t quite understand what the problem could be, unfortunately, especially since I can’t replicate it locally with the same PHP version.
I’m a bit lost on this as well. I guess it’s a matter of deactivating plugins here locally to see if anything is conflicting.
So, testing locally with a default theme (Twenty Twenty-Two) and only the core Broadcast plugin active is still giving me the error locally.
I tried creating a new post, broadcasting it, and then opening the dialog.
On the demo site I have almost the same setup: WP 6.3, PHP 8.1 and 2023 as the theme instead of 2022.
No problems finding unlinked children nor unlinking.
Would you like me to log in and take a look for myself? Please send me the login details to edward@plainviewplugins.com
Thanks @edward_plainview! About the only other item I can think of that may make a difference is that both local and production are Nginx servers. Could that be at all relevant?
Unfortunately I can’t give direct access to the site. But I can probably set you up to tunnel into my local install. I’ll be in touch!
This has been resolved with 50.05 – thank you!
