Meta Box

Support Forum » User Profile

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • September 5, 2024 at 5:24 PM in reply to: Cloning broken #46337
    digitaalitoimistodigitaalitoimisto
    Participant

    Yes, thanks you! Please hurry with it, lots of problems with it as it breaks the content if someone saves a post with cloneable fields.

    September 5, 2024 at 5:21 PM in reply to: text_list type saved values not displaying in backend #46336
    digitaalitoimistodigitaalitoimisto
    Participant

    This is bug related to cloning, the forum has multiple entries and the latest version is completely usable currently. Please revert back to 5.9.11 if you can, it works.

    This issue has been since multiple days and to my knowledge no response from the team. This is bad for the product, which is a shame. metabox has been our go to plugin for ~200 projects but now I'm reverting all of them back and lots of problems with broken content due to this bug. If this was tested before release none of this would have happened. Perhaps the team has changed?

    September 4, 2024 at 3:03 PM in reply to: Cloning broken #46323
    digitaalitoimistodigitaalitoimisto
    Participant

    Well, description is wrong in my first post 😀
    Here illustration of key_value field. On 5.9.10 it's working, see this screenshot with var_export of $meta:
    Working with version 5.9.10 var_export showing data structure saved in post meta.

    Here same with 5.10.0 and there is extra array layer added at some point, also empty string as first item, and now the fields do not show in the metabox because the array structure is different what the output code expects.
    Not working, there is extra array layer and also empty string at the beginning. Now the output functionality doesn't work with this data and metabox doesn't show the saved fields. Metabox version 5.10

    In both of the images data in database is what is shown in the first attachment, without extra array layer. The data was saved with 5.9. but saving data on 5.10 doesn't work either, it goes fine into database but var_export for $meta shows the same bad data structure.

    Here is how the code looks to reproduce both the images above.
    Piece of code to reproduce the above images

    As per your blog post https://metabox.io/clone-empty-start/ and comments in code let believe this empty values are added only when there is no data saved in database, but this is clearly not the case.

    Please fix the bug asap. Thanks.

    September 3, 2024 at 1:25 PM in reply to: Bug Metabox 5.10.0 #46311
    digitaalitoimistodigitaalitoimisto
    Participant

    Perhaps related issue, key_value field is broken due to how code handles cloning.

    September 3, 2024 at 1:23 PM in reply to: Big issue with cloneable fields #46310
    digitaalitoimistodigitaalitoimisto
    Participant

    key_value metabox is also broken, problem with cloning in code, perhaps related.

    May 31, 2023 at 5:03 PM in reply to: Editing Featured Image on CPT causes warnings #41992
    digitaalitoimistodigitaalitoimisto
    Participant

    Why there is no edit 😀 cumbersome

    May 31, 2023 at 5:02 PM in reply to: Editing Featured Image on CPT causes warnings #41991
    digitaalitoimistodigitaalitoimisto
    Participant

    Ugh, bold didn't work inside code and cant edit 😀 remove the tags of course, so the line should be
    return get_current_screen() && get_current_screen()->id === 'attachment';

    May 31, 2023 at 5:01 PM in reply to: Editing Featured Image on CPT causes warnings #41990
    digitaalitoimistodigitaalitoimisto
    Participant

    Meanwhile, if its annoying, add the bolded part to the file and line in the error

            
private function is_attachment_edit_screen(): bool {
  return <strong>get_current_screen() &&</strong> get_current_screen()->id === 'attachment';
}
    August 17, 2018 at 2:53 PM in reply to: ✅Meta Box plugin call un-needed query ? #11033
    digitaalitoimistodigitaalitoimisto
    Participant

    Noticed this as well, I've got >60k posts :S

    It seems that the 'post' field, that allows selection of a post, metabox will query all available options for the field on every request. I think it should query available options only when the actual meta box field is being rendered.

    I'm not using metabox frontend functions so I was able to narrow this problem to dashboard only by not registering metaboxes on the frontend requests.

  • Author
    Posts
Viewing 9 posts - 1 through 9 (of 9 total)