Forum Replies Created
-
AuthorPosts
-
Ryan Lauritsen
ParticipantLong Nguyen, when will this fix be ready?
This has totally screwed up our data coming through multiple front-end forms and we need an immediate fix. Do I need to revert to an old version or is there a change I can make to the code to revert this temporarily until a fix is released.
Ryan Lauritsen
ParticipantAnh, does this apply to fields hidden via the CSS
display: none;?We have some fields that are hidden using that method but still need validation (they are populated programmatically with some custom javascript). It was working fine but this or some other recent change has broken it. If I remove
display: none;the validation works.Ryan Lauritsen
ParticipantIt sounds like your issue is different.
The issue described in this thread was breaking the form/page completely, preventing anything after the field from loading. That was fixed quite a while ago in Meta Box version 4.18.4.
I would suggest starting a new thread so support can help with your issue.
Ryan Lauritsen
ParticipantYes, we are using the Frontend Submission extension. I'd like the fields to show up both on the frontend and in admin (replacing the default WP UI fields). The reason is that we are trying to customize how data is input in the admin with metabox fields instead of default WP fields.
March 17, 2020 at 3:47 AM in reply to: ✅Bug: Frontend form submit button stuck as disabled when validation fails #18557Ryan Lauritsen
ParticipantThank you, Anh Tran!
Ryan Lauritsen
ParticipantAnything?
Ryan Lauritsen
ParticipantMaybe a better question is... Can we access the search term typed into a
select_advancedfield within thequery_argsparameter so that we can create a more sophisticated search query?Ryan Lauritsen
ParticipantThanks, Anh Tran. I've got it working now. Is it possible to customize the data being searched? For example, have it only search the email and not URL, username, or display_name?
January 21, 2020 at 11:09 AM in reply to: ✅MB User Profile not working because of latest MB User Meta #17930Ryan Lauritsen
ParticipantI can confirm that this is also true on our site. Thanks for tracking it down and posting this @luisdelcid
Ryan Lauritsen
Participant@Anh
What was your final decision on this?
Going forward if'readonly'=>truewill the datepicker show or not?From your last post, it sounded like the datepicker will NOT show but I just want to confirm that since I'll have to make some changes on my end if that's true. Thanks!
November 2, 2019 at 12:09 AM in reply to: Thumbnail field in frontend form allows any file type #16773Ryan Lauritsen
ParticipantI tried the following and it didn't work.
add_filter( 'rwmb_frontend_post_thumbnail', function( $field ) { $field['attributes'] = [ 'accept' => 'image/*', 'oninvalid' => "setCustomValidity('Please select an image file.');", ]; } );Ryan Lauritsen
ParticipantWhy was this "fix" even needed? If you don't want the datepicker, then don't use a date field. Use a text field instead. If it has to do with forcing a date format, then either use validation on a text field to force the format or maybe we need an option to turn the datepicker on/off for date fields.
Ryan Lauritsen
ParticipantUnfortunately, we were using the fact that it ignored readonly to get around the lack of format control for the date entered into the input. We had date fields set to readonly to force users to use the datepicker so that we forced the format of the date to be our preferred format. Otherwise, we had users entering years as 2 digits (e.g. 01/01/20 instead of 01/01/2020) which doesn't work for us.
This fix has prevented the workaround we were utilizing so how can we now force the year to be 4 digits? We already have the
dateFormatattribute set tomm/dd/yybut that doesn't prevent a user from typing a date with only 2 digits. We also have thesave_formatfield setting set toY-m-dand that doesn't help either. I've searched the jQueryUI documentation and not found a solution.October 31, 2019 at 1:34 AM in reply to: Thumbnail field in frontend form allows any file type #16749Ryan Lauritsen
ParticipantThank you, Anh. This works well. Can I customize the error message shown when attempting to upload a non-image file?
Currently, it says:
Please enter a value with a valid mimetype.Ryan Lauritsen
ParticipantAnh, can you confirm if this is a bug?
-
AuthorPosts