Saving changes to ACF gives warnings with plugin active

  • Resolved danyw18

    (@danyw18)


    7 months, 4 weeks ago

    Plugin version 1.4.5

    With plugin active, every time I make a change to Advanced Custom Fields (add/update a custom post type, change ACF settings) I get a screen full of warnings (see attached) for “Undefined array key “f” and “Cannot modify header” in ajax.php.

    Debug Code: BMI-c630vLve-73727

    https://i.imgur.com/Zax8mSe.png

    • This topic was modified 7 months, 4 weeks ago by danyw18.
    • This topic was modified 7 months, 4 weeks ago by danyw18.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author iClyde

    (@iclyde)

    Hi @danyw18

    Thank you for reporting, not sure how it’s possible, we use special syntax for our calls, but we fixed this particular issue in this release:

    https://backupbliss.com/downloads/plugins/bmi-betas/backup-backup-1.4.5.2.zip

    Let me know if that resolves your issue ??
    Thank you!

    Plugin Support MixHa

    (@mixha)

    Hello @danyw18 ,

    We haven’t heard from you since, so I’ll assume that the issue is resolved and will close this support thread. If you face any new issues, please feel free to open a new thread.

    Kind regards

    I’ve got the same issue on my setup running WordPress 6.5.5. I was getting the exact same warnings as @danyw18 shared in his screenshot when running version 1.4.5 of the plugin. I downloaded the beta that you linked to above, version 1.4.5.2 and that helped to suppress many of the warnings but one still plagues my logs as a new warning gets added for practically any action I take in the WordPress admin.

    PHP Warning: Undefined array key "f" in /home/user/Local Sites/mysite/app/public/wp-content/plugins/backup-backup/includes/ajax.php on line 62

    It’s not causing any issues but I’m writing a lot of code for a custom theme and this warning fills my debug logs which is rather irritating after a while. Would you be able to provide any insights as to why this warning keeps coming up, and perhaps any steps that I could take to resolve the issue? Or is there perhaps an updated version of the plugin where this issue has been fixed?

    Thanks for your time,

    Regards.

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