Support » Plugin: Advanced Custom Fields: Extended » does not what it says

  • This plugin looks that is helpfull and actually extends the ACF , but its not except probably in some easy solutions even without this plugin.

    It says that has Bidirectional , but that thing is not working with fields that are grouped or in a repeater.. Such a waste of time.

    If i am missing something i would be more glad to change the review , but i have wasted 2 hours with it and i see that it will not work unfortunately.

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

    (@hwk-fr)

    Hello,

    Well it’s been one hell of a ride! 2 years of hard work, 75 five star reviews, +800 lines of changelog, +700 support answers. I knew this day would come sooner or later, so here we are.

    So it looks like you’re struggling with the Bidirectional Setting. First thing first, it works with Groups fields (and Clones too), as described in the documentation.

    Here is a video showing the feature with Grouped <> Grouped, and Grouped <> Ungrouped relationships. Here is an another video showing it with Multi Sub Groups <> Grouped relationships.

    Regarding the bidirectional setting in Repeater/Flexible Content, this option is not sustainable and flawed by design, since it would make no pratical sense. Here are some examples:

    Case 1: Data from Post 1 change all rows on the related Page

    +-----------------------------+---+-----------------------------+
    |           Post 1            |   |           Page 1            |
    +-----------------------------+---+-----------------------------+
    | Row1: Relationship          | / | Row1: Relationship (Post 1) |
    | Row2: Relationship (Page 1) | > | Row2: Relationship (Post 1) |
    | Row3: Relationship          | \ | Row3: Relationship (Post 1) |
    +-----------------------------+---+-----------------------------+
    
    +-----------------------------+---+-----------------------------------------+
    |           Post 2            |   |                 Page 1                  |
    +-----------------------------+---+-----------------------------------------+
    | Row1: Relationship          | / | Row1: Relationship (Post 1? or Post 2?) |
    | Row2: Relationship (Page 1) | > | Row2: Relationship (Post 1? or Post 2?) |
    | Row3: Relationship          | \ | Row3: Relationship (Post 1? or Post 2?) |
    +-----------------------------+---+-----------------------------------------+
    
    • How can the system understand that it should take the Page 1 from Row2 and not the (Empty) from Row1 or Row3? What makes it more reliable than any other rows? What if you simply wanted to remove the relationship and set the latest value as empty? Shouldn’t it take the latest empty save and clear Page 1?
    • If we have an another Post 2 which set a relationship with Page 1, should it erase all previous rows? Since the bidirectional is configured to be applied to all rows?
    • If we remove the Post 1 from a Row1 in Page 1, what should the system do with other rows in Page 1? Should it clear all rows? otherwise there would be a desync and no more data consistency.
    • As the system is bidirectional, then the same rule should apply in both ways, which means all rows of Post 1 should have Page 1 value for consistency. Which makes the whole system useless, since it would be more optimized to have a simple classic field with a bidirectional setting.

    Case 2: Data from Post 1 change the related row on the related Page

    +-----------------------------+---+-----------------------------+
    |           Post 1            |   |           Page 1            |
    +-----------------------------+---+-----------------------------+
    | Row1: Relationship          |   | Row1: Relationship          |
    | Row2: Relationship (Page 1) | > | Row2: Relationship (Post 1) |
    | Row3: Relationship          |   | Row3: Relationship          |
    +-----------------------------+---+-----------------------------+
    
    • What if there is no Row2 in Page 1? Should it create the row to set the relationship, with other sub fields as empty? What should it do if other sub fields are required?
    • Same as above, what if we have an another Post 2 which set a relationship with Page 1 on Row 2, should it erase the previous row value?

    Case3: Only update the first row of the related row on the related Page

    +------------------------------+---+-----------------------------+
    |            Post 1            |   |           Page 1            |
    +------------------------------+---+-----------------------------+
    | Row1: Relationship           |   | Row1: Relationship (Post 1) |
    | Row2: Relationship (Page 2)  | / | Row2: Relationship          |
    | Row3: Relationship (Page 1)  | | | Row3: Relationship          |
    +------------------------------+---+-----------------------------+
    
    • As above, collision problem if we have a Post 2 trying to set a new relationship with Page 1. Should the system erase the previous value?
    • It’s an edge case, even if it works for you, that will probably not make sense for other users.

    That was the answer in substance. Now for the form, you’re probably new to WordPress & ACF community (your account has been created 9 months ago), so I’ll try to not be too tough.

    The simple fact that you gave an initial 3 star rating to the ACF plugin, which is by far the most powerful plugin of the WordPress directory, shows you don’t really understand this whole ecosystem.

    ACF Extended, the bidirectional setting, and all other advanced features were built for developers, because it imply complex logic, require some abstract thinking and also some modesty. The fact that you didn’t post a support question, but go straight to “2 star review” because “you lost 2 hours” and decide to punish this plugin without even asking anything, just show you don’t fit the mindset of the ACF Extended community.

    Now regarding the sentence “This plugin looks that is helpfull and actually extends the ACF, but its not except probably in some easy solutions even without this plugin.”:

    The Flexible Content: Dynamic Preview alone just blow away any other attempts to provide a consistent pagebuilder solution for the Flexible Content, by far. And I didn’t even mention other features like the ACFE Forms or the Single Meta Save… The Bidirectional Setting on it’s own is already ahead any other bidirectional tutorials/plugins, because it’s compatible with groups & clones, allow you to set self-relationship (a field related to itself), use custom names etc…

    As a conclusion, I would have been happy to help you to setup a bidirectional system for your use case, as I often do with the other users (I have a working code with Repeater/Flexible Concept, but didn’t release it since it’s flawed by design, as explained above). But your review, which is very borderline (“If i am missing something i would be more glad to change the review”), is just a big red flag. I prefer to focus on the plugin development and help users of the community.

    Now I don’t expect much from you. I would be happy if you just drop ACF Extended, find a working tutorial and use your own solution.

    I wish you the best luck for your journey in the WP community.

    Regards.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.