After Upgrading PublicPress Permissions (Version 4.7.0) getting ACF nonce issue

  • Resolved aaresrikanth

    (@aaresrikanth)


    1 week, 3 days ago

    Hi,

    I am encountering an issue with the Advanced Custom Fields (ACF) plugin after upgrading to the latest version of the PublicPress Permissions plugin (Version 4.7.0). Previously, everything was functioning correctly, but after the upgrade, I started receiving the following error when updating a custom post type post:

    “Validation failed. ACF was unable to perform validation because no nonce was received by the server.”

    This issue occurs when trying to save or update posts that include custom fields created by ACF. It seems that the recent update of the PublicPress Permissions plugin (Version 4.7.0) has caused this conflict with the nonce validation in ACF.

    ACF Plugin Version : 6.7.1

    WordPress Version : 6.9.1

    I suspect the conflict is related to the PublicPress Permissions plugin update, which is affecting the nonce validation process in ACF.

    Could you please assist in investigating and resolving this issue? Any help or guidance on how to fix this would be greatly appreciated.

    Thank you for your time and support. I look forward to your prompt response.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Riza Prihananto

    (@rizaprihananto)

    1 week, 3 days ago

    Hi @aaresrikanth ,

    Thank you for using the PublishPress plugin.

    Could you take a look at the following screen record related to your issue?
    https://drive.google.com/file/d/1k-CmeiQj96DtF538yY15QGXm4ZUtp_Hs/view?usp=sharing

    We would also like to have more information regarding your site, such as:
    – Theme that you applied
    – The user role that updates the custom post type
    – Custom field that you included in the custom post type

    By having all of these, we may be able to recognize the issue since we can at least adjust the testing environment.

    Thread Starter aaresrikanth

    (@aaresrikanth)

    1 week, 2 days ago

    Hi Riza Prihananto,

    Thank you for your immediate response.

    Please find the attached screenshots for your reference. I would like to inform you that I am updating the post as an administrator using the Twenty Twenty-Five theme. I have also attached the relevant custom fields for your review.

    Kindly look into the issue and assist with a resolution.

    https://drive.google.com/drive/folders/1_FpYWjGCclLQmoXMCDcyN339eYRdRgHy?usp=sharing

    Plugin Author Richa Ferry Setyawan

    (@aakricha)

    3 days, 2 hours ago

    Hi @aaresrikanth ,
    Thank you for your report. But after doing testing with your information, unfortunately i’m still can’t replicate your issue. We will happy to help you fix if you can provide staging site. Because we can’t replicate your issue in our environtment.

    View post on imgur.com

    Thanks

    Thread Starter aaresrikanth

    (@aaresrikanth)

    2 days, 18 hours ago

    Hi @Richa Ferry Setyawan

    Thank you for your continued support on this matter.

    After checking from our end, we identified that the issue was occurring due to a large number of custom meta fields on the page, which exceeded the default PHP input variable limit.

    We have now resolved the issue by increasing the value of the max_input_vars parameter to 5000 in the php.ini configuration. After making this change, the functionality is working as expected.

    Thank you once again for your assistance.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.