Support » Plugin: Advanced Custom Fields: Extended » Single Meta Save: Fields missing

Single Meta Save: Fields missing

  • Resolved keksbln

    (@keksbln)


    3 years ago

    Hi,

    I tried out the feature “Single Meta Save” for a customer.

    Latest versions von WP, ACF Pro and ACFE (and Timber).

    First: It speeds up saving a page with a lot of ACF fields (in our case up to 1000) alot – most times. Sometimes saving the page is slow again.

    Second: It is a bit annoying, that many fields are delivered in a different structure, so that I have to change the PHP and/or Twig code. The structure is better than with pure ACF, but it changes, when enabling this feature. Therefore I need both variants in my code and switches like “if (is_array($modules)) { … } else { … }”.

    Third: After updating the code step by step, one of the last pages did not work. ACF/ACFE is not returning some subfields. 🙁

    Here is my debug output, where I can see several fields missing, sometimes partly:

    Hmpf… No screenshot pasting possible here? 🙁

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter keksbln

    (@keksbln)

    3 years ago

    So here is my debug output:

    array ( 'acf_fc_layout' => 'abo_page', 'view' => 'landingpage', 'opener_image' => 18201078, 'teaser' => array ( 'left' => array ( ), 'center' => array ( 'bubble' => array ( 'text_large' => '10', 'text_small' => '5 für 10!', ), ), 'right' => array ( ), 'special' => array ( 'bubble' => array ( ), ), ), 'links' => array ( 0 => array ( 'name' => 'Studententarif', 'elements' => array ( 0 => array ( 'typ' => 'text', 'text' => 'Sie studieren? Dann nutzen Sie unseren', 'icon' => false, 'abo_slug' => '', 'zeitraum_slug' => '', ),

    … and so on. Fields are missing in “teaser.left”, “teaser.center”, “teaser.center.bubble” (1 of 3 is missing), “teaser.right”, “teaser.special” and “teaser.special.bubble”.

    Thread Starter keksbln

    (@keksbln)

    3 years ago

    The debug output screenshot:
    https://preview.unitb.com/ja/acfe_sms_bug_output.png

    These are the ACF fields / this is the input (part of):
    https://preview.unitb.com/ja/acfe_sms_bug_input.png

    The checkbox field (with two possible values) is also missing (internal name “enabled”).

    The ACF structure is quite complex, because I implemented a module system using ACF flexible content (= “modules”) with several modules. This page has only one module configured (an “abo page” module).

    Thread Starter keksbln

    (@keksbln)

    3 years ago

    Ahhh… when I rename the field “teaser” (e.g. to “teasers”) and fill out all subfields again, then it works.

    When I do this, then the customer has to do this on production system after deployment.

    So it’s not a problem with the field structure, but maybe with converting existing values!? About the two “bubble” fields, which are returned: I can not change the value. I can, I see the new value in the backend, but in the frontend I still get the old values. Weird.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    3 years ago

    Hello,

    Thanks for the feedback. The Single Meta Save works correctly on complex Flexible Content here, I also use it on many production websites. There’s probably something wrong in your configuration.

    I cannot really help you with this flexible content, as it is far too much complex and I’m not in your head 🙂 In order to isolate the problem, you should create a new flexible content with more simple structure and try to trigger the bug, then export the field group so I can download & test it on my side.

    Regards.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    3 years ago

    BTW, you can join us on the ACF Slack community, using this invitation link: https://join.slack.com/t/wpacf/shared_invite/enQtODc2MjczMzM3NzQ1LTQxNmY2ZGY3OTU2NDkxNTliYmNhMmY1NDMwZGM4NmYxNzgwZTI5MDUzMDFlMGQ5YzcwNDc0ZWM0MDVmODI4NmI

    It will be easier to discuss and share screenshots there 😉

    Regards.

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    3 years ago

    Hello,

    Just to let you know that the latest 0.8.6.3 Update include a rework of the Single Meta Save codebase. It may fix your issue, please update the plugin and let me know.

    Regards.

    Thread Starter keksbln

    (@keksbln)

    3 years ago

    I “solved” the problem by renaming the field, because the update to 0.8.6.1 did not help. So I cannot reproduce it anymore. And therefore I think, that creating “a new flexible content with more simple structure” would not reproduce the problem.

    Thanks for your feedback!

    Plugin Author Konrad Chmielewski

    (@hwk-fr)

    3 years ago

    Hello,

    The last Update 0.8.6.3 introduced a new codebase for that module, which is now even more integrated in ACF logic. I also tested it on my complex flexible content page builders. There shouldn’t be any problem.

    Anyways, I’m glad to hear that your issue is solved now.

    Have a nice day!

    Regards.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Single Meta Save: Fields missing’ is closed to new replies.

Views