• Hi. First: Thanks for the hard and brilliant work. Buying ACF Extended was a good choice.

    But I have a problem: Many had this before, but I didn’t find a solution yet.

    I have different post types called for example “Instruments”, “Audio”, “Video”, etc…
    In the backend of the different CPT’s I have tabs and groups for better optics. One of the group is called “Relations” with different Relationship Thingies. Those are set to “Bidirectional”. And this works. When I select a post, it becomes Bidirectional related.
    BUT: In every post type I do have also other groups and some of the information of the object I choose as a related object goes missing. Informations from Repeaters. When they are top level, they just vanish in the backend.
    When they are nested in a group, they don’t vanish in the backend but aren’t there in the front-end, as long as I don’t go into the post edit and update the post again. But this happens not only to repeaters nested in groups, but for example to chosen values of Radio Buttons as well. I can see the correct choice in the backend, but before I Update the post again (even without any changes done), they behave, as I would have chosen the first value.

    How can I avoid this behaviour?

    Best
    Martin

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Thanks for the feedback!

    It will be quite complex to understand what is causing the issue without having more details. Maybe the problem come from Groups & Sub Fields using the same name which could produce some conflict. For example, if you have a Group called group and a sub field called text, then the sub field metadata name will be named group_text. If you create an another top-level field named group_text, then there will be a conflict between them during the save. This is just an hypothesis tho.

    The best way to check your metadata iunformation is to enable the Developer Mode, as it will give you a very useful overview of the meta that are saved on the current page. I would recommend to enable it and check if everything seems alright there.

    I just made some tests on my end using a similar Group + Relationship fields, and it works fine. Video of my test: https://i.imgur.com/8S1GO6A.mp4

    If the problem doesn’t come from here, maybe you could post some screenshots of the meta overview as it may help to understand your setup. You could also try to setup a simple test like I did in my video with new “Test Post Types” and “Test Field Groups” with unique field names, just to make sure it works correctly, and then add new fields one by one.

    Hope it helps!

    Have a nice day!

    Regards.

    Thread Starter Martin M. Meier

    (@mmm44)

    thx. I will try it out and come back here. It will take a few days.

    Until then

    Martin

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Okay! Let me know when you get something new!

    Regards.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Any news?

    Regards.

    Thread Starter Martin M. Meier

    (@mmm44)

    hey. I needed a few days for my other work. Sorry. Here is a video of the problem:

    https://kaspardornfeld.de/Data/video.mp4

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Support note: After a discussion with the user, the problem was caused by a conflict with multiple groups using the same name on the same post type screen. See answer #14959091.

    Regards.

    Thread Starter Martin M. Meier

    (@mmm44)

    Yeah. I can agree to that. In my different post types I had for example a group called “file_group”. Since I renamed them by giving it a prefix according to the different post types, the problem is gone.

    Best and THANKS for the help!

    Martin

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Bidirectional Relationsship kill group field content in related object’ is closed to new replies.