Support

Account

Home Forums Bug Reports Clone field bug in 5.4 RC1

Solving

Clone field bug in 5.4 RC1

  • Hello

    We are using v5.4 RC1 – I hope this is the correct forum.

    I think we’ve found a bug with cloning and prefixing a field in options, and just want to provide feedback.

    If we use a normal field with a field prefix, everything is fine
    If we use a normal field without a field prefix, everything is fine

    If we use an option field with a field prefix, the field doesn’t save (the field stays blank when I save rather than it not rendering within the template)
    If we use an option field without a field prefix, it seems fine

    Here is a screencast of the theme option saving when not prefixed, and not saving when prefixed: https://www.dropbox.com/s/5njmi25ec5914bb/clone.mov?dl=0

    We’ve managed to reproduce on 2 installs.

    Thanks!

    Doug

  • Yes, there are still bugs in the clone field. The version you’re using is a Beta. The developer is already aware of the issue.

    For bug reports, the best way for to get them to the developer is to submit a new ticket here https://support.advancedcustomfields.com/new-ticket/

  • Can anyone confirm this bug still exist in v5.4.1?

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

You must be logged in to reply to this topic.