Support » Plugin: Meta Box » Quick Edit not working (and problem located)

  • Resolved mingyeungs


    When you open ‘Quick Edit’ and click on ‘Update’, the message “Are you sure you want to do this?Please try again.” appear, and the changes cannot be saved.

    After some digging it’s found to be nonce verification issue. The problematic code located on line 433 of


    . If you remove the line check_admin_referer( "rwmb-save-{$this->meta_box['id']}", "nonce_{$this->meta_box['id']}" ); then the post will save without issue.

    Please fix this in later release? thanks a lot!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Just noticed that removing the line “check_admin_referer” would cause another issue, that is, custom meta will be erased after you click on ‘Update’ in ‘Quick Edit’ mode.

    A workaround (no sure if it’d cause other problem though…), is to add

    || ( $_POST['action'] == 'inline-save' )

    after line 426 of


    In this case, the ‘save_post’ filter will not be applied when user quick edit a post.

    Still, waiting for official update from the plugin author to solve this problem.

    I click on “Quick Edit” and nothing happens.
    Then when I go to edit page and try change visibility, I click on ‘edit’ next to word ‘private’ and page jumps but nothing else happens.
    This is after updating wordpress this morning. Have a backup but am hoping for a fix instead.

    I believe the correct fix is to add the check for inline-save as mingyeungs suggests above. But you should leave in the check_admin_referer line to prevent unauthorized edits to your pages.

    The problem is that the meta-box save_post function is called on a quick edit, but the rwmb-save nonce is not created, nor are the fields populated in memory. So the save_post function must quit without checking the nonce and without updating the fields to prevent their being blanked out.

    Plugin Author Tran Ngoc Tuan Anh


    Fixed in version 4.2.4.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Quick Edit not working (and problem located)’ is closed to new replies.