Meta Box

Fields not saving

Support › General › Fields not savingResolved

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 3, 2021 at 11:19 PM #29872
    Topher DeRosiaTopher DeRosia
    Participant

    At some point in the last couple days field values have stopped saving. I can't think of anything that would do that except I upgraded to WP 5.8. I tried rolling back with no luck. I only have about 8 fields, so it doesn't seem like it should be max field count. I'm not getting anything in the error log, no errors on the front end. Other things in the item save, like title, taxonomies, and status. This is a custom post type. Where could I look to debug this?

    I'm currently running WP 5.8 and
    MB Settings Page
    Version 2.1.3

    Meta Box
    Version 5.4.6

    MB Conditional Logic
    Version 1.6.14

    August 4, 2021 at 10:01 AM #29879
    Long NguyenLong Nguyen
    Moderator

    Hi Topher,

    This issue is so weird. Please try to deactivate all plugins except Meta Box, MB Extensions and switch to a default theme of WordPress to re-check the issue.

    If this procedure does not help, please share the code that creates meta boxes and custom fields on the CPT page. I will try to check it on my end.

    August 4, 2021 at 8:58 PM #29889
    Topher DeRosiaTopher DeRosia
    Participant

    That didn't help. Here's my code: https://drive.google.com/file/d/1l0s_K5QJ059RxGSDd4v5xKSltwx5VbsA/view?usp=sharing

    August 5, 2021 at 10:57 AM #29911
    Long NguyenLong Nguyen
    Moderator

    Hi,

    It is possible that the fields are not saved value caused by this code

    if ( empty( $_GET['post'] ) ) {
    return;
}

    it should be return $meta_boxes;

    You can try to remove this block of code or function casa_rejection_reasons then re-save the field value.

    August 5, 2021 at 9:27 PM #29927
    Topher DeRosiaTopher DeRosia
    Participant

    That was exactly it! Thank you so much.

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