Support

Account

Register Login

Forum Replies Created

  • Oh, I didn’t realize this thread was accidentally submitted twice, sorry for that.

    In the other one with the same title I think I already answered my own question, which wasn’t about the nonce value generated in the form field, but the value returned in the $_POST.

    I found this with respect to the latter:

    According to this document listing acf code –

    https://docs.wpdebuglog.com/plugin/advanced-custom-fields/5.8.8/function/acf_verify_nonce/

    acf resets the nonce to “false” upon verification so the form can only be submitted once with this nonce. So “false” as value for ‘acf_nonce’ in the $_POST actually means ‘verified’, if I’m not mistaken.

    Although I wonder if changing “false” to “verified” for “acf_nonce” in the $_POST may make it easier to understand what is going on?

    Thanks for your reply!

  • Hi,

    is there by now a way to only show one row of a repeater field?

    My problem is this: I’m trying to build a math quiz for spam protection for a front end form.

    So I’d need to select one random pair of question and answer from a repeater field in an options group, display the question field in the form and then validate the input value against the answer in the specific repeater row.

  • Just answering my own question in case someone needs this info:

    According to this document listing acf code –

    https://docs.wpdebuglog.com/plugin/advanced-custom-fields/5.8.8/function/acf_verify_nonce/

    acf resets the nonce to “false” upon verification. So “false” as value for ‘acf_nonce’ in the $_POST actually means ‘verified’.

  • “I’m not sure how much time I’ll have to dedicate to a solution but would love to continue the conversation!”

    Same here, I’ll see how much of this development can be a part of an upcoming project.

  • I have the same problem. Conditional display of fields does not appear to work in the gutenberg sidebar.

    Has there been a solution in the meantime?

  • Thanks! Now it works.

    The following is only partly related, but I was wondering about the possibility of a migration option that would not just create the field structures but also allow to translate the flexible field layout order and contents of layouts into acf-blocks.

    I’m still early in my learning about Gutenberg and its way of doing things, but what I think I’ve understood is that, so far, most of the processing is done in JS on the client side, including saving acf custom field values, which makes programatically generating blocks from layout-content difficult. Changes to the block api are intended but there’s no eta.

    While researching this, I came accross the following recent post linking to an experimental php block-serializer in the gutenber plugin, and now I’m wondering if that may not present a solution to automatic migration of acf flexible layouts into blocks.

    https://wordpress.stackexchange.com/questions/343037/how-to-serialize-a-gutenberg-block-from-block-attributes-in-php

    If possible, given this plugin’s purpose, I thought this may be of interest.

  • I just went through the acf code and it appears these are custom functions, which would explain the problem.

  • I tracked the problem down to the convert_layout method. It’s constantly throwing a 500 error as AJAX response if any of the “acf_” functions (like acf_get_field_id) are called. Is there anything that needs to be done to the installation or ACF before using this plugin?

  • Thanks for that!

    I’m trying to convert an existing “page builder” structure into blocks, but I keep getting “conversion error” when I click on “convert to block” for all existing layouts in the flexible content field.

    I’m not sure it’s not my fault, though, as I’m a bit unsure how to go about using the plugin.

    I’ve enabled “auto blocks” in the settting area of the flexible content field, I’ve assigned a block key (and added a template file of the same name to the theme root), I’ve picked an icon and enabled multiple blocks, resusable blocks, and all alignments.

    On save the chosen Icon and block-selector will appear in the admin interface, but no actual content is displayed. As mentioned above, attempting to convert a layout by choosing “convert to block” in the backend layout options menu will lead to a js-error window “conversion error”.

    Also, I notice that a new condition for the display of the flexible field (show if block equals all) is added everytime the field gruop is saved…

  • @elliot,

    thanks, I managed to get rid of the warning! Thanks for pointing me in the right direction.

    Works like a charm now!

    If anyone is interested: I’ve replaced the x-profile-field loop in community>members>profile>profile-loop.php with the fields/form generated by ACF for the fields I’ve entered in the WP user profile. That way I can keep the Buddypress structure and features while benefitting from the amazing conditionality features of ACF. For this project I can live without the visibility controls of x-profile fields since all profiles will be visible to all internal users.

    Thanks again Elliot!

  • Oh, I just realized that the image upload/edit/delete links don’t work in the front end either.

  • Thanks Elliot!

    I’ve modified my Buddypress profile-loop.php with an acf-form and the fields are displayed nicely (as per

    -http://www.advancedcustomfields.com/resources/tutorials/creating-a-front-end-form/
    -http://support.advancedcustomfields.com/forums/topic/front-end-and-custom-user-meta/
    ).

    I’m getting this warning though –

    Warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/www/…/html/beta/wp-content/plugins/advanced-custom-fields/core/api.php on line 1168

    And it appears there’s a problem with the conditionality. I assumed that the admin-js that is responsible for handling the conditionality aspect in the backend would be loaded through acf_form, but apparently that’s not the case – at least the conditional fields are all displayed regardless of the entered values. Is there any way to achieve this (short of rewriting the conditionalities in jquery)?

    If it is possible, Which scripts would have to be enqueued for this to work?

    Thanks for a brief reply!

  • Thanks for the quick reply!

    I managed to get some fields on the WP user-profile edit screen now. Thanks a lot!

    So, since I don’t have those 5 months for this project and I need conditionality, I’m thinking – wouldn’t it be possible to replace the bp xprofile loop with a loop of the acf-added WP user_meta (and, possibly, for the edit view, put it in a form and update it from the front end?)

    Thanks again!

  • Hi Elliot,

    thanks for the great plugin – one question: I’m currently working on a community install of WP/BuddyPress. I hadn’t looked at BP for a while because the integration with WP wasn’t as good as I had hoped for, particularly with respect to

    I’m a bit confused about ACF’s capabilities with respect to custom user meta.

    In a couple of threads on the support forum it reads as if it is currently possible to use ACF to input custom user_meta fields on the profile page –

    http://support.advancedcustomfields.com/forums/topic/capabilities/
    http://support.advancedcustomfields.com/forums/topic/common-custom-field-for-user-profile-and-post/
    http://support.advancedcustomfields.com/forums/topic/buddypress-user-profile-fields/

    while on this one it says it’s impossible in the current version. If it is currently possible, could you point me to a tutorial about how to add an appropriate location rule because I apparently am unable to get it working, even trying the custom technique outlined here –

    http://www.advancedcustomfields.com/resources/tutorials/custom-location-rules/

    Maybe my grasp of the plugin’s structure is insufficient, but I can’t get this done.

    If it is currently impossible to do this as appears to be stipulated by this thread, is it possible to indicate a time range when it might be?

    Thanks for a brief reply!

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