The only way to resolve is to get the actual request data that is getting blocked. You can use the code inspector of your browser to get the information.
Hi @gregburnison, just wanted to follow up with this. It’s been awhile with no reply, so I hope the issue is resolved? Or if there is anything I can do to help, please let me know. Thank you.
Thread Starter
gb.wp
(@gregburnison)
Hi Jeff,
Thanks for following up. I hadn’t looked at this yet.
Using the ACF Quick Edit Fields plugin lists all the fields I have set to add to the quickedit function. In this case I only made a change to the first field, changing it to “NEW VALUE”.
The path for request is:
/wp-admin/edit.php?s=&post_status=all&post_type=clinic&_wpnonce=6797c539c7&_wp_http_referer=/wp-admin/edit.php?post_type=clinic&action=edit&cat=0&author=0&filter_division=all&clinic_name=all&layout=5e98b87ca8076&paged=1&post_category[]=0&tax_input[post_tag]=&post_author=-1&_status=-1&acf[field_5e8b206fb9883]=NEW+VALUE&acf[field_5e6f942a37751]=___do_not_change&acf[field_5eea105e51bb1]=___do_not_change&acf[field_5ea04b4a779bc]=___do_not_change&acf[field_5eea108951bb2]=___do_not_change&acf[field_5eb55e241c5ea]=___do_not_change&acf[field_5e6f94a337752]=___do_not_change&acf[field_5e8b20adb9884]=___do_not_change&acf[field_5fee60e9fcb45]=___do_not_change&acf[field_5eda11a5dd0ad]=___do_not_change&acf[field_5eda121add0ae]=___do_not_change&acf[field_5eda1221dd0af]=___do_not_change&acf[field_5eda1225dd0b0]=___do_not_change&acf[field_5eda122add0b1]=___do_not_change&acf[field_5eda122cdd0b2]=___do_not_change&acf[field_5eda122fdd0b3]=___do_not_change&acf[field_5eda1236dd0b4]=___do_not_change&acf[field_5eda123bdd0b5]=___do_not_change&acf[field_5eda1240dd0b6]=___do_not_change&acf[field_5eda1245dd0b7]=___do_not_change&acf[field_5eda1247dd0b8]=___do_not_change&acf[field_5eda124add0b9]=___do_not_change&acf[field_5eda124fdd0ba]=___do_not_change&acf[field_5f224ea3a603d]=___do_not_change&acf[field_5e8b22d2c5674]=___do_not_change&acf[field_5e8b241cc5675]=___do_not_change&acf[field_5e8b2430c5676]=___do_not_change&acf[field_5e8b2445c5677]=___do_not_change&acf[field_5e8b245fc5678]=___do_not_change&acf[field_5e8b2470c5679]=___do_not_change&acf[field_5e8b24b8c567e]=___do_not_change&acf[field_5e8b247ec567a]=___do_not_change&acf[field_5e8b24c4c567f]=___do_not_change&acf[field_5e8b248bc567b]=___do_not_change&acf[field_5e8b24cec5680]=___do_not_change&acf[field_5e8b2496c567c]=___do_not_change&acf[field_5e8b24d9c5681]=___do_not_change&acf[field_5e8b24a1c567d]=___do_not_change&acf[field_5f224ef2a603e]=___do_not_change&bulk_edit=Update&post_view=list&screen=edit-clinic&post[]=4446&post[]=5160&action2=-1
Is this what you’re looking for?
Thanks. I just tried that URL on default WordPress with BBQ *deactivated* and it was blocked. So not sure if BBQ is involved at this point, will do some more testing and report back.
Just to follow up with this, the reported request URI is blocked by BBQ because of its length. By default, BBQ blocks any excessively long requests (over 2,000 characters). To allow such requests, you can install the super lightweight BBQ Customize Plugin, specifically this section explains how to use, etc. Let me know if any questions, glad to help anytime.
