Meta Box

Error saving the location of a custom field.

Support › MB Builder › Error saving the location of a custom field.Resolved

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • February 4, 2021 at 7:33 PM #24323
    Nuno CruzNuno Cruz
    Participant

    When editing a CUSTOMIZED FIELD, in the SETTINGS tab, the POST location, when changing to display the fields in another POST TYPE, after saving, does not save the change and always returns to the POST location. This error occurs in old custom fields after some change. Apparently the new ones don't have this problem.

    February 4, 2021 at 8:36 PM #24324
    Nuno CruzNuno Cruz
    Participant

    I did more editing tests for PERSONALIZED FIELDS and verified that no settings in the SETTINGS tab are saved.

    February 5, 2021 at 12:26 PM #24336
    Long NguyenLong Nguyen
    Moderator

    Hi,

    Thank you for your reporting.

    I'm going to discuss with the developer team to take a look at this case and create an update to cover it.

    February 6, 2021 at 8:39 PM #24349
    Nuno CruzNuno Cruz
    Participant

    I hope you notice how harmful this error is for the good use of this wonderful plugin. I simply cannot assign custom fields to my Post Types.

    February 8, 2021 at 10:04 AM #24368
    Anh TranAnh Tran
    Keymaster

    Hi Nuno, can you give more details on "Customized field" and "Personalized field"? Are they custom field types?

    Please share some screenshots of the issues.

    February 8, 2021 at 8:45 PM #24386
    Nuno CruzNuno Cruz
    Participant

    Please, see this video:

    https://www.loom.com/share/821ed22a8c3b40ae9acf646631e0a00d

    February 9, 2021 at 8:48 AM #24394
    Anh TranAnh Tran
    Keymaster

    Hi Nuno,

    Can you try editing settings for any field and see if it can be saved? If not, then I think the problem is the number of inputs exceed the PHP limit. If that's the case, please see the solution here:

    https://metabox.io/wordpress-custom-fields-not-saving-increase-max-input-vars/

    February 9, 2021 at 10:27 PM #24408
    Nuno CruzNuno Cruz
    Participant

    Anh Tran

    First thanks, it worked.

    Second:
    I just received an update and noticed that the year on the update dates is like 2020.

    February 19, 2021 at 3:12 PM #24491
    Anh TranAnh Tran
    Keymaster

    Thanks a lot for the 2nd thing! I've fixed the dates in our changelogs!

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