Some Custom Fields Not Saving after WP/MB Update (not max_input_vars issue)

Support General Some Custom Fields Not Saving after WP/MB Update (not max_input_vars issue)Resolved

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #43752
    brandonjpbrandonjp
    Participant

    Some of my custom fields have stopped saving. I've encountered this before, so I assumed the issue is related to the PHP setting max_input_vars -- However, then I checked my sites phpinfo and max_input_vars is already set to 100,000 ! https://cln.sh/j14ktNgQ

    Some of the fields are saving, but some are not. The issue started after I ran updates:
    * Theme: Twenty Nineteen - Updated from version 2.5 to 2.6
    * Plugin: Meta Box - Updated from version 5.6.17 to 5.8.2
    * Plugin: MB AIO - Updated from version 1.19.1 to 1.23.1
    * WP Core: Updated from version 5.9.7 to 6.3.2

    Here is what I've tried:
    * increasing max_input_vars (currently it is 100,000)
    * checking 'Save Field Value' (true on all fields)
    * plugin conflicts (disabling all other plugins does not resolve the issue)
    * using default theme (does not resolve the issue)
    * switching custom fields from php code to MB Builder (no effect)

    Before I go down the path of reverting to previous versions of MB & WP, do you have any other ideas of what the issue might be?

    Thank you.

    #43754
    brandonjpbrandonjp
    Participant

    I have new information!

    I could only find a few older versions of MB AIO, but I was able to narrow it down a lot.

    meta-box-aio-1.21.1 ❌ - did not save
    meta-box-aio-1.20.2 ✅ - did save correctly

    Somewhere between AIO v 1.20.2 and 1.21.1, something changed that seems to be preventing some of my fields from saving. I'm guessing it might have to do with changes to MB Custom Table, as seems to be the only extension I'm using that had significant changes. https://metabox.io/plugins/meta-box-aio/changelog/#:~:text=1.20.2

    This might not be entirely a MB problem, as the project I'm working on was my first ever to use MB, so it's very possible I've done something wrong that just happened to work until now 🤷‍♀️ Here is how I'm creating metaboxes: https://pastebin.com/x3hbhqbx

    #43756
    PeterPeter
    Moderator

    Hello Brandon,

    What are custom fields that stop saving value on your site? If I remove the revision setting and increase PHP settings max_input_vars to 500k and I can save field value as well.

    #43766
    brandonjpbrandonjp
    Participant

    Hi Peter, thanks for the reply.

    When I'm using meta-box-aio-1.21.1 any field below line 388 https://pastebin.com/x3hbhqbx fails to save.

    But when using meta-box-aio-1.20.2 all fields save with no changes to max_input_vars or revisions

    I've been able to replicate this on Dreamhost shared hosting and Rocket & Flywheel hostings.

    #43771
    PeterPeter
    Moderator

    Hello,

    Thanks, I see it works with MB AIO version 1.20.2. I've escalated this issue to the development team to take a look. I will get back to you later.

    #43816
    brandonjpbrandonjp
    Participant

    Hi Peter, I have an update.

    ❌ When using meta-box-aio-1.21.1 on WP 6.3.2 it does not work.
    ✅ When using meta-box-aio-1.21.1 on WP 6.4.1 it DOES work! 🤷

    Right now I'm using the latest of everything and it works correctly:
    ✅ MB 5.8.2 and AIO 1.23.1 and WP 6.4.1

    Just wanted to let you know. 🙂

    #43821
    PeterPeter
    Moderator

    Great. Thanks for letting me know.

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