Support Forum ยป User Profile

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Having some issues on the new AIO update. #49124
    RobertRobert
    Participant

    Of course. My apologies, I didn't notice it in the rush.

    https://pastebin.com/DAkkpiFP

    in reply to: Having some issues on the new AIO update. #49117
    RobertRobert
    Participant

    Sure thing, here is goes (first time using pastebin)

    https://pastebin.com/G1Nx4wiM

    in reply to: Having some issues on the new AIO update. #49109
    RobertRobert
    Participant

    Regarding "When editing custom fields, I get same random fields prompting me to fill in values now.", I realized some findings that might be helpful.

    I had 2 clone-able URL fields with conditions that were both placed in different areas, but each of those conditions were set to a field that didn't exist. I deleted both of these URL fields completely before realizing that maybe having a condition set to a non-existent field might be the culprit but I don't know.

    I also removed the "required" validation from the text and WYSIWYG fields. I lastly refresh the cache entirely (LSCASHE, OBJECT, etc.).

    The form now works without it prompting me to fill in the details when editing the custom fields in Metabox.

    Is this all expected behavior?

    in reply to: Having some issues on the new AIO update. #49108
    RobertRobert
    Participant

    Regarding "how can I have a custom taxonomy connect to a CPT via a tax / advanced tax field", it is not a bug.

    I learned there are nuanced differences between tax. and adv. tax fields, its placement requirements, and how it saves data from this post: https://support.metabox.io/topic/how-to-set-taxonomy-terms-from-multiple-taxonomy-fields/#post-38573

    However, I tried using the code in this forum answer from Peter: https://support.metabox.io/topic/syncing-group-taxonomy-advanced-field-with-a-taxonomy-field/

    Does the code presented on March 28, 2023 at 7:38 PM work for cloneable groups or have internal workings changed? It doesn't seem to work for me.

    in reply to: Having some issues on the new AIO update. #49107
    RobertRobert
    Participant

    Edit for above post: if I set my fields as cloneable as above, it makes my original CPT item non-editable with a blank white screen.

    If I set my fields without a cloneable tax. adv. field, I can edit my original CPT item without a blank white screen.

    Does not seem to fix the need to fill in my fields to save when editing the fields however.

    in reply to: Having some issues on the new AIO update. #49106
    RobertRobert
    Participant

    Good day! ๐Ÿ™‚

    I was exploring reasons why the taxonomy advanced field doesn't set the post term, and I learned that if I set my custom fields as below for a CPT, my original CPT item white screen goes away and becomes viewable:

    |-Clonable Group
    |--Text Field
    |--Cloneable Taxonomy(color) (only allow one taxonomy to be selected) value=red
    __________________
    |--Text Field
    |--Cloneable Taxonomy(color) (only allow one taxonomy to be selected) value=blue

    If I remove the clone ability from the taxonomy advanced field, the white screen for the original item goes away. Is this expected behavior?

    in reply to: Having some issues on the new AIO update. #49101
    RobertRobert
    Participant

    I also tried deactivating everything and switching themes from Bricks Builder.
    Latest Metabox AIO update (with tax reordering) / WP: 6.8.3 / PHP: 8.4 / Brave Browser

    This is a big priority for me since this is my portfolio website that I need to get a job / get contract work since I've been laid off recently ๐Ÿ™

    I tried several things in those videos I recorded with Zight, so thank you for your patience viewing them!

    in reply to: Having some issues on the new AIO update. #49100
    RobertRobert
    Participant

    By the way, I love Metabox!!! Happy day to you ๐Ÿ™‚

Viewing 8 posts - 1 through 8 (of 8 total)