Forum Replies Created
-
AuthorPosts
-
Yasmine
ParticipantUnderstand 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?
ParticipantOk 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)
ParticipantIn your screenshot you do not look like you tried to save it with valid values
ParticipantThank you for testing! I deleted that staging site. But the issue was when trying to save the values (so when it is validated, it will not save as it if thinks there are no values - when there are values). If you don't have that as an issue on your demo site, I will set up another staging to show you
ParticipantHi Peter.
I upgraded from 5.9.11 to 5.10.1 and 1.29.0 to 1.30.1 in a staging site and unfortunately the issue still there.
But when only upgrading the Meta Box AIO to 1.30.1 - issue not there (although it starts clone count at 0 rather than 1). But no issue with save. So it is definitely it was definitely introduced by the Metabox 5.10. The 1.30.1 is just doing something strange to the clones but I don't think the core issue
Thanks,
YasmineParticipantI don't think MetaBox read the replies in threads (my experience - anyway) . I think better to open another ticket so they are sure to see these
ParticipantGreg, I tried disabling every required field and removed all validation, but it still does not work. Apparently the workaround is to save all the clones as empty until the fix next week. Apparently also there will are no database issues caused by rolling back to 5.9.11
ParticipantReverting back to AIO 1.29.0 did not fix it, but reverting back to 5.9.11 did
ParticipantHi - I can restore a backup of the last metabox but there have been loads of database changes using cloneable groups, taxonomies, other custom fields. Will it work if I revert back??
Participant* I tested by reverting back to meta-box-aio-1.29.0.zip - not to Version 5.9.0 ....
August 28, 2024 at 10:21 PM in reply to: Access previous versions of Meta Box AIO via Composer #46271ParticipantIt would be so helpful to always have access to the last one or two versions via a link in our account!
ParticipantOr if no direct filter, another filter which allows me to modify the image before save?
ParticipantIt was the
'child_of' => 10152,causing the issue.This was what I needed, but the child filter stopped everything working
ParticipantThanks - it now works
ParticipantOk understood. Yeah I did do lots of experimenting already with classes. But the conditional formatting of other fields would then override mine. Even though I was using a display: none!important
-
AuthorPosts