Support

Account

Forum Replies Created

  • I meant that it would be nice to have a filter on the admin screen that lists all of the field groups 🙂

  • +1 from me as well. Wrapper attributes are only available when displaying the clone field in a group, however, this complicates how you access the field.

  • Good to know! Thanks

    I could see this potentially causing some confusion for less savvy users editing a relationship field if they were to select only draft posts (as no posts would appear on the front end)

  • That makes sense! Thanks John.

    I’m now wondering if I were to select a draft post when I retrieve the field on the front end will that draft post be included? The main thing that I would worry about is accidentally displaying draft posts on the front end that should not be public

    Going to test this today

  • I would like to report that I’m experiencing the same issue. A front end ACF form is used to create a pending CPT and contains image fields. The uploaded images show up in the List view in Media Library but not in the Grid view. So they are successfully uploaded and for the most part very much the same as any other image – I’ve not been able to pinpoint the difference by looking in the database so far.

    Unfortunately switching the uploader to the ‘WordPress’ media uploader isn’t a good solution for this site because we don’t want the users to be able to browse and select images that are already in the Media Library.

    My client noticed it out for the same reason as OP’s client – they needed to add the image to another field. WordPress uses the Grid View for the Media Library that pops up when attaching images to fields or adding them to the WYSIWYG, so the images can’t be added to any other fields.

  • I’d like to chime in and say that I’m having the same/similar issue. (Actually my problem is the exact same as the other support thread that was linked in the original post.)

    The main reason I use the conditional logic this way is that it can be very difficult to re-order repeater rows if they have more than one or two small fields, as dragging and dropping becomes almost impossible when each repeater field row fills up most of the screen.

    I’m going to experiment with using the built-in feature of collapsing repeater fields instead.

  • Hi John,

    I had extensively googled the issue and multiple times ran into this max_input_vars suggestion so I had already tried adding the following lines in my .htaccess file:

    php_value max_input_nesting_level 128
    php_value max_input_time 300
    php_value max_input_vars 3000
    php_value max_execution_time 300
    php_value post_max_size 32M

    Unfortunately this didn’t seem to help with my particular problem.

    I have found that after I was able to change the field keys back to what they were supposed to be set as from phpmyadmin the fields were saving again. (I looked them up on the staging server where the field keys were still correct since I hadn’t updated the field group)

  • I’ve made an important discovery – all fields are having their field keys overwritten when they are updated or created:

    Creating a new field:

    Creating a new field

    New field after saving the field group:

    New field after saving the field group

  • Hi everyone,

    I would like to add my voice to David’s call to please add the relevant information that David and John have shared here to the documentation as soon as possible! It wouldn’t take long and it would do a world of good to anyone trying to use repeater fields with acf_form() securely.

    Yesterday I spent hours trying to figure out why my front-end form’s repeater fields wouldn’t save! I had followed the security guidance provided in the documentation and didn’t think to question it. This particular thread did not come up in my searches, so I had to figure it out on my own. The only reason I found this thread actually is because I was planning on posting my findings on this issue myself.

    Thank you very much for the information that you both have provided on how we can keep our forms secure while still retaining the functionality of the repeater fields.

  • Hi @elliot

    Thanks. I had seen that. I tried integrating it into the code that I have working but I’m not experienced enough with mySQL and PDO and I’m at a loss of how to go about it.

  • Hi @elliot

    My project is a blog where they will periodically be posting featured weddings. It is a custom with these types of blogs that they will have a list of acknowledgements at the bottom of the post that tells the reader where they got the cake, the flower arrangements and things like that.

    I thought the repeater field would be perfect since the size and contents of the list could differ greatly from post to post.

    Since this can still be easily input via a custom field with a WYSIWYG editor, it’s not worth the time/trouble to figure out how to make the repeater fields searchable for me at this time.

    I -am- still using the repeater field for these same blog posts so that the blogger can create a photo gallery (though in hindsight my client would’ve been better off if I went with the Gallery plugin for this project instead).

    Once I found out the way that repeater fields are stored in the database, mycustomfield_0_mysubfield, mycustomfield_1_mysubfield, and soforth, I thought if I could somehow return a list of those meta_keys so that I could put them in my array of custom fields it might work…

    eg. $custom_fields = array(‘mycustomfield_0_mysubfield’, ‘mycustomfield_1_mysubfield’);

    But it would differ depending on the post… so I’m not sure if that would work. Here is my code: pastebin

  • Hi @elliot

    So it’s throwing the error at line 628 of field-group.js

    Uncaught TypeError: Object [object Object] has no method ‘sortable’
    field-group.js?ver=4.2.2:628

    fields.addClass(‘sortable’).sortable({
    update: function(event, ui){
    update_order_numbers();
    },
    handle: ‘td.field_order’
    });
    });

  • Hi @elliot,

    I just wanted to let you know that I’ve discovered that, in creating a new Field Group today the drag and drop re-order is working. It’s just on the one that was created before the update that it doesn’t work!

    It’s also not really a huge issue for me anymore – I’ve got things in the order that I need them to be. But I will keep working with you to help find a solution to this error if you would like.

  • Hi @elliot, sorry I should’ve thought to include that. Unfortunately the line number won’t help as it’s a minified file.. any ideas?

    Uncaught TypeError: Object [object Object] has no method ‘sortable’ field-group.min.js?ver=4.2.2:1

  • Hi @elliot
    yes I’ve performed lots of hard refreshes..

    Console log reveals the following error:

    Uncaught TypeError: Object [object Object] has no method ‘sortable’

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