Forum Replies Created
- AuthorPosts
joeblow44444444
Participantclever enough to go with for now, thanks.
February 3, 2023 at 8:25 am in reply to: can’t select html fields when creating conditional logic #35127joeblow44444444
Participantdidn’t realize hidden field was required for this, got it.
February 2, 2023 at 8:42 am in reply to: can’t select html fields when creating conditional logic #35118joeblow44444444
Participantneither group ids nor column ids show as conditional options either.
joeblow44444444
Participantthis worked, thanks
joeblow44444444
Participantthis worked, thanks
joeblow44444444
Participantexcellent, worked. thanks again.
joeblow44444444
Participantthanks but i should have been more specific. primarily needing responsive width and height per separate instances of the widget in separate forms on the same site.
i.e., quforms on two pages, one page is full width and another is two column. while the quforms on those pages are responsive, the calendar is always the same relative size and in the same relative position. how do i adjust each one’s width, height, position and responsiveness?
joeblow44444444
Participantthat did it, thanks very much.
yeah there’s a proxy method to circumvent the xss cors thing but that’s outside the scope of quform.
off topic but is there ever going to be a way to style the kendo time and date pickers?
joeblow44444444
Participantnone of the above. however, i was able to get the jquery virtual keypad to type into quform fields and the data is saved to entry dbase and emails. two things are still failing:
1) the preview page will not populate any field where data was entered via the keypad. have tried multiple iterations and combinations of blur, change, click, keydown, triggerhandlers, selectors, etc.
2) the keypad will not type into the stripe integration card element field.
maybe you’ll see something i don’t below.
keypad jquery example:
$(document).ready(function () { let input_1 = $(".quform-field-101_398"); // have tried let, const, var $(".quform-field-101_398").keydown(function () { return false; // have tried true }); $(".calc").click(function () { let value1 = $(this).val(); fieldfirst(value1); }); function fieldfirst(value1) { input_1.val(input_1.val() + value1); } $("#clear").click(function () { input_1.val(""); }); $("#bkspc").click(function () { input_1.val(input_1.val().slice(0, -1)); }); });
keypad html example:
<input type="button" value="A" id="A" class="pinButton calc"/> <input type="button" value="B" id="B" class="pinButton calc"/> <input type="button" value="C" id="C" class="pinButton calc"/> <input type="button" value="D" id="D" class="pinButton calc"/> <input type="button" value="E" id="E" class="pinButton calc"/> <input type="button" value="F" id="F" class="pinButton calc"/> <input type="button" value="G" id="G" class="pinButton calc"/><br /> <input type="button" value="H" id="H" class="pinButton calc"/> <input type="button" value="I" id="I" class="pinButton calc"/> <input type="button" value="J" id="J" class="pinButton calc"/> <input type="button" value="K" id="K" class="pinButton calc"/> <input type="button" value="L" id="L" class="pinButton calc"/> <input type="button" value="M" id="M" class="pinButton calc"/> <input type="button" value="N" id="N" class="pinButton calc"/><br /> <input type="button" value="O" id="O" class="pinButton calc"/> <input type="button" value="P" id="P" class="pinButton calc"/> <input type="button" value="Q" id="Q" class="pinButton calc"/> <input type="button" value="R" id="R" class="pinButton calc"/> <input type="button" value="S" id="S" class="pinButton calc"/> <input type="button" value="T" id="T" class="pinButton calc"/> <input type="button" value="U" id="U" class="pinButton calc"/><br /> <input type="button" value="V" id="V" class="pinButton calc"/> <input type="button" value="W" id="W" class="pinButton calc"/> <input type="button" value="X" id="X" class="pinButton calc"/> <input type="button" value="Y" id="Y" class="pinButton calc"/> <input type="button" value="Z" id="Z" class="pinButton calc"/> <input type="button" value="clear" id="clear" class="pinButton clear"/> <input type="button" value="back space" id="bkspc" class="pinButton bkspc"/><br />
joeblow44444444
Participanthow do i get the data typed into the custom input fields to go to the database and emails? anyone?
joeblow44444444
Participantsome progress with jquery, but data entered into the input fields doesn’t show up in email or entries. {all_form_data} simply sends the actual empty input fields from the form instead of the values entered into the input fields. not finding clear guidance in the docs.
joeblow44444444
Participantbreaks it. ended up renaming the id selectors, worked for first input but not the rest. thinking there’s some way to use only quform functionality to accomplish this, just not smart enough to figure it out. this is for a form on a browser locked touchscreen, can’t use os virtual keyboard because it contains special characters, spacebars, tabs, etc, as well as methods of circumventing browser lock.
anyway i need each field in the step-page form (first name, last name, email, phone, etc) to have its own virtual keypad to enter alphabetic or numeric characters into the input fields. i played with layouts of checkboxes or radio buttons labeled a-z and 0-9 styled into grids under each input field, but can’t figure how to correctly pass the characters to the input fields, and still wouldn’t be able to select any letter/number more than once or a backspace button to delete a typo, for instance.
jquery plugins seem promising, but to integrate with quform they require a lot of customization that’s apparently over my head. any suggestions?
January 13, 2018 at 8:06 pm in reply to: please help prevent past and current date from being chosen #23867joeblow44444444
Participantwhat about for multiple forms?
January 11, 2018 at 2:55 am in reply to: please help prevent past and current date from being chosen #23814joeblow44444444
ParticipantAs it turns out, the reason I couldn’t find the solution was because I have version 2 but for whatever reason the documentation only refers to version 1. I eventually found the version 2 method you noted above, but wasted a lot of time to do so.
January 8, 2018 at 1:55 am in reply to: please help prevent past and current date from being chosen #23735joeblow44444444
Participanti did see this in the documentation but don’t understand what i’m supposed to do with the extra numbers such as 10, 4
function my_datepicker_prevent_past_dates($options, $dpMinYear, $dpMaxYear, $element) { return "{ minDate: 0, maxDate: new Date({$dpMaxYear}, 12 - 1, 31) }"; } add_filter('iphorm_datepicker_options_iphorm_1_1', 'my_datepicker_prevent_past_dates', 10, 4);
- AuthorPosts