Error while saving posts on subsite

  • Resolved naturfreundeschweiz

    (@naturfreundeschweiz)


    1 month, 2 weeks ago

    We run a multisite setup and installed Powered Cache yesterday. Users on subsite got the following error message when trying to make a new post. This was on a custom post type but I did not test if it also happens on a normal post.

    The update failed. Unfortunately, you are not authorized to edit the custom field powered_cache_disable_cache.

    If I look into the network tab I get the following answer:

    {"code":"rest_cannot_update","message":"Du bist leider nicht berechtigt, das individuelle Feld powered_cache_disable_cache zu bearbeiten.","data":{"key":"powered_cache_disable_lazyload","status":403},"additional_data":[{"key":"powered_cache_disable_cache","status":403}],"additional_errors":[{"code":"rest_cannot_update","message":"Du bist leider nicht berechtigt, das individuelle Feld powered_cache_disable_lazyload zu bearbeiten.","data":{"key":"powered_cache_disable_lazyload","status":403},"additional_data":[{"key":"powered_cache_disable_cache","status":403}]}]}

    With ChatGPT I managed to get it running with the following code but thats surley not ideal:

    add_filter('user_has_cap', function($allcaps, $caps, $args, $user) {
    if (defined('REST_REQUEST') && REST_REQUEST) {
    if (!empty($_SERVER['REQUEST_URI']) && strpos($_SERVER['REQUEST_URI'], '/wp/v2/posts') !== false) {
    if (isset($allcaps['edit_posts']) && $allcaps['edit_posts']) {
    $allcaps['manage_options'] = true;
    }
    }
    }
    return $allcaps;
    }, 999, 4);

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mustafa Uysal

    (@m_uysl)

    1 month, 2 weeks ago

    Hi @naturfreundeschweiz,

    Thanks for the report.Did you activate Powered Cache network-wide, or only on a per-site basis?

    Users on subsite got the following error message when trying to make a new post. This was on a custom post type but I did not test if it also happens on a normal post.

    Could you share the affected user’s role on that site?

    At the moment, a user must have the edit_others_posts capability to modify cache-related settings on a specific post, so this may be a capability-related issue. I’ve tested this on multisite with standard Administrator and Author roles and did not encounter the problem. Normally, users without the required capability should not see the Powered Cache section in the block editor at all.

    Looking forward to your reply.

    Thread Starter naturfreundeschweiz

    (@naturfreundeschweiz)

    1 month, 2 weeks ago

    Thank you for the fast answer! You are correct: It is a custom role made with the “Admin Menu Editor Pro” plugin. It does NOT have the edit_others_posts capability so that seems to be the problem

    It is correct though, that this role should not be able to edit posts from other users. I do not see a Powered Cache section with that role (which is good) but I do get the error message. Attached you see a screenshot of the capabilities of the role.

    https://nfsenioren.ch/wp-content/uploads/sites/68/2026/02/FireShot-Capture-004-Menu-Editor-Pro-Roles-‹-Naturfreunde-Senioren-Zuerich-–-WordPress_-nfsenioren.ch_-scaled.png

    Plugin Author Mustafa Uysal

    (@m_uysl)

    1 month, 2 weeks ago

    Hi @naturfreundeschweiz,

    Thanks for confirming, that explains it.

    I think the real issue here is not the failed capability check itself, but why the failed REST request ends up blocking the post update entirely.

    For example, when creating new categories or tags, if a user does not have the required capability, that specific request fails — but the post update itself is not blocked. So in this case, something else may be interfering with how the failed API response is handled.

    Since this is a custom role created via Admin Menu Editor Pro, it’s possible another plugin is affecting the REST behavior or capability handling.

    Thank you for the fast answer! You are correct: It is a custom role made with the “Admin Menu Editor Pro” plugin. It does NOT have the edit_others_posts capability so that seems to be the problem

    Yes, that part is expected behavior — without edit_others_posts, the meta update should fail. However, it normally should not prevent the post from being saved.

    For now, I’ll mark this as resolved from our side. If you continue to experience the issue or narrow it down further, feel free to reopen the thread and I’ll be happy to take another look.

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

You must be logged in to reply to this topic.