Big issue with cloneable fields

Support MB Group Big issue with cloneable fields

Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #46435
    YasmineYasmine
    Participant

    In your screenshot you do not look like you tried to save it with valid values

    #46438
    PeterPeter
    Moderator

    Here https://imgur.com/vpDLOx5
    I add some test values and it is saved as well.

    #46440
    YasmineYasmine
    Participant

    Ok I rechecked and the issue is now just my own JS. But please see the video so I can demonstrate that how I validate with JS now no longer works: https://jam.dev/c/f8d9026d-9e20-47ed-80bb-6d98f61df7ee

    Staging site was created just now, but the only difference is the MB versions (staging is latest)

    So this check no longer works?

        
    !$('input[name="academicfindings[0][academicfinding]"]').val().trim()) { ....} 
    

    Has the index changed perhaps? Or a way to check validation in js ?

    But as shown in the video, it was working and just the MB change that is failing this test.

    (And I must admit that I assumed the new version was not working as this js was not working when I tested it - and this js not working was a symptom of when it didn't work in the last version, but it does submit now - just the js)

    #46451
    PeterPeter
    Moderator

    Hello,

    So it's not an issue of Meta Box itself. The cloneable item now starts the index from 1. You can try to change the index from 0 to 1 and see if it helps.
    academicfindings[1][academicfinding]

    Also note that, supporting a customization code is beyond our scope of support. If you want to use a customization service, please contact us here for more details https://metabox.io/contact/

    #46453
    YasmineYasmine
    Participant

    Understand that the issue I faced in 5.10.1 was due to the index changing. Did the indexs change for other things too? Eg - taxonomies? I have a lot of code that grabs the first index in custom ways. Was it just cloneable fields the index changed for? Are they likely to change again?

    #46462
    PeterPeter
    Moderator

    Was it just cloneable fields the index changed for?

    Yes, only the index of the cloneable field is updated from Meta Box version 5.10.0.

    Are they likely to change again?

    I'm not sure about that, but the index is updated from the new version.

Viewing 6 posts - 16 through 21 (of 21 total)
  • You must be logged in to reply to this topic.