Cloned field values ??are no longer displayed on form

  • Resolved 1Spirit23

    (@1spirit23)


    5 months, 1 week ago

    Hello,

    Defects have appeared since the application of version 0.9.0.5: the data displayed by cloned fields no longer appear.

    Context of the project :

    • A first group of fields has been added to the user profile (Back Office): member number, membership start date, title, date of birth, telephone numbers, etc.
    • A second group of fields has been created (no location rules have been mapped). It includes, in the form of cloned fields, part of the fields from the first group: phone numbers, address, town/city, etc.

    The second group is used by an ACFE form which offers a front-end editable form for connected members.

    The observations:

    Without being able to say precisely, we believe that everything worked correctly at least until version 0.9.0.2. or even version 0.9.0.4

    No error message appears (debug to true). We assume this is an issue with ACF Extended: we will post on the ACF/ACF Pro support forum based on your feedback.

    The form is integrated into a page using a shortcut: the result is the same regardless of its form of integration into the page – [acfe_form ID=””] or [acfe_form name=””]

    For testing, we integrated the form on a page outside of the access control system available to the site: the result is the same.

    The faults:

    Since applying the latest version, the loaded data (additional profile data) appears in the back office but no longer appears on the front-end form (the “native” profile data – last name, first name, etc. .. – are correctly displayed).

    We managed to make the data reappear (see screenshot) – on a field duplicated for the tests – by modifying the “Display format” configuration of the cloned field, by passing the option “replace this field with the selected fields” to “group” (shows the selected fields in a group within this field).

    Additional information which does not call into question the bug but which is useful to take into consideration:

    Having checked some member profiles on the front-end (we emphasize the conditional of the following information): it seems that the data which has already been modified from the front-end form by the members is displayed.

    Thank you in advance for your feedback and corrections: we remain at your disposal for any additional information.

    Best regards

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter 1Spirit23

    (@1spirit23)

    Here is the screenshot

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Thanks for the feedback and the detailed report.

    In fact, I was able to reproduce the issue. There has been some changes in how values are loaded in the recent updates, and this was an oversight. This is kind of an edge case tho, since you try to load a clone from a user, but the clone itself doesn’t exist on the user (it’s the fields inside the clone that exist on the user).

    A more classic way to handle this use case is to map 2 Field Groups in your Form. 1 Field Group with front-end fields, and 1 Field Group with the User profile fields directly. And then if you want to change the fields order, or hide some fields, you would use the “Render” setting (see documentation).

    I’m adding a fix in the next patch. In the meantime, you can fix it by yourself following these instructions:

    In the file /acf-extended/includes/acfe-helper-functions.php line:573, find this code:

    // return
    return $value;

    And replace it with this code:

    if($is_seamless && empty($value)){
        $value = null;
    }

    // return
    return $value;

    This will correctly load the clone seamless fields from the outsourced target.

    Sorry for the inconvenience, and thanks again for the report.

    Regards.

    Thread Starter 1Spirit23

    (@1spirit23)

    Hi Konrad,

    Many thanks for your feedback and correction : it works fine !

    We agree with you: we also, partially, came to the same conclusion ??

    To make a long story short, the current solution was implemented starting from the existing one: We will most likely make changes in this direction soon, i.e. make the necessary modifications to the field groups to match them to the needs of the front-end form.

    Have a nice day !

    Best regards

    Rapha?l

    Thread Starter 1Spirit23

    (@1spirit23)

    Note: time to carry out some additional checks and I will mark the thread as resolved !

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Awesome!

    I’m glad to hear it now works as expected!

    Have a nice day!

    Regards.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Just a heads up to let you know the latest ACF Extended 0.9.0.6 version fixed this issue.

    Have a nice day!

    Regards.

    Thread Starter 1Spirit23

    (@1spirit23)

    Hi Konrad,

    Version 0.9.0.6 applied… everything works fine!

    Very good continuation to you, with my greetings!

    Rapha?l

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.