Forum Replies Created
- AuthorPosts
- August 8, 2018 at 12:23 am in reply to: Edit Entry mode doesn't display validation errors on ['save'/submit] #26579
katw
ParticipantHi Ally, There’s a little confusion.
I am this time not talking about conditional fields. Just fields in Edit Entry mode and whether the field element validation (if set) is also applied in this environment.
My case:
I have a simple text field with element settings that check Digits, Length min 11 and length Max 11.
This is NOT a hidden field or conditionally shown field. So put that thought away. I know I have been on that topic for a while but not this time 😉
On SAVE no error message shows under the field to say “Too long”, “Too short” or “Just numbers please”.
So, I was wondering if the error message functions exist in Admin mode?
As I am seeing nothing, only an “Entry Saved” on click [save/submit]. Yet- the illegal value is (thankfully) not saved.
katw
ParticipantClose ticket
katw
ParticipantHi @generail. Thought I could help out
Issue 1 – After you put correct information, do you click Submit again?
Or are you expecting the message to go away on field exit / field change?Error checking occurs at form submit not on field click/change events.
Issue 2 – Is this Android or iPhone?
I have checked a form I have built on IOS and Android and the tooltips appear on click.
Perhaps a script error is preventing it from working.
Have you checked the Developer console for javascript error messages?
katw
ParticipantHi @damti, thought I could help out.
You can hide the field label by either:
- Leaving the field label empty (no text = no label)
- Using CSS style option in the field settings OR add a style to your theme. The easiest way is using the field settings if just hiding a few labels. HOW? Follow these steps:
- Edit field with the label you want to suppress
- Click [STYLES] tab on Element Settings window
- Click [Add a style] button at bottom under CSS Styles
- Choose
Label-Text
as selector (if you want to hide the label but not tooltip) orlabel
(to hide label and tooltip) - Type
display:none;
in the CSS box - Save
The important thing to work out is whether you need or want the Required asterisk ‘*’ or Tooltip to still show in the absence of a label.
To keep the field required asterisk on show you will need to add further custom CSS override. As this markup is also hidden when you use either selector as described above. This is because the HTML markup for ‘Required’ is inside the label tag.
See how you go.
katw
ParticipantHi Ally,
Could you add a new field setting for HTML ELEMENT to allow user to provide a ASCII / Plaintext version of their field data.
This field will be used in PLAIN-TEXT email part.
Right now any HTML field shows ugly raw code in plaintext emails if “show in email” toggle is on.
Obviously output logic would fall back to the primary HTML field if
Plaintext field = empty
andemail type = plaintext or multipart
Thanks
Attachments:
You must be logged in to view attached files.katw
ParticipantThought I had done that. But upon inspection it was in a row/column construct.
Thanks for that suggestion. Will try it out.
katw
ParticipantYes thanks. All good. Close ticket
August 6, 2018 at 1:35 pm in reply to: Notification emails Date and Time not using defined regional settings #26547katw
ParticipantThanks again Ally.
Close Ticket
katw
ParticipantThat was where I was going to suggest next; check the browser developer console for error messages.
If you see nothing when clicking on the cog it means something is blocking or intercepting the dialog overlay operation.
Great work. Especially picking up on which plugin to turn-off so quickly.
katw
Participant@arkofhope I’ll see if I can help.
What are you seeing when you click the cog icon on the NAME FIELD?
And just to be sure.. check you have added a Field Element type of NAME… not a TEXT element by accident.
This is what I see when I click the cog. I am using V2.x.x of QuForm.
- This reply was modified 6 years, 9 months ago by
katw. Reason: Added screenshot
Attachments:
You must be logged in to view attached files.August 4, 2018 at 12:46 am in reply to: add_filter('quform_get_value_html') funct skipped when field empty & listEntry #26524katw
ParticipantAwesome. Thanks. Close ticket
katw
ParticipantHi Ally,
Following on from that code example (which is perfect for my needs too) …
If you replace the
config('description')
withconfig('label')
you could output the label text – correct?And for the admin label you would use
config('adminLabel')
– correct?Thanks
katw
ParticipantHi Ally,
An old discussion but my problem isn’t solved by your suggestion.
Hidden fields can’t be conditionally hidden or shown like other fields can.
A field that is conditionally visible has an extra benefit; they remain hidden in Entry View even if the “show empty fields’ checkbox is enabled.
Hidden fields become visible when empty AND “Show empty fields” is active; even if these fields do not apply.
Use case:
- Contact by: radio field with choices: Phone, Email
- On choosing “Phone” a Phone number field is shown; otherwise phone field not shown.
- Imagine a hidden field called “Phone INT format”; which contains a calculated value based on the phone field.
- This field IS CONTEXTUAL and is only relevant if “Phone” is “Contact_by” choice.
- On viewing an entry with “Phone” being the Contact method you see Phone Number field and Phone INT format field – GOOD
- On viewing entry without “Phone” as Contact method and “View empty fields=true” you don’t see Phone Number field but still see Phone INT format field – BAD
The Phone number field doesn’t show and it was empty… but its companion hidden field is visible.
Would be great to have conditional show and hide available to hidden fields; or a way to remove these fields from Entry View when they don’t apply.
katw
ParticipantOn further investigation the wrong hook is being used to coerce the validator a submit.
BEFORE:
quform_entry_pre_process_#
.This is not run at form submission/processing but used with edit entry form.
AFTER: Changing the hook to
quform_pre_process_#
solved the issue and allowed the form to be submitted with an option value outside prescribed range.Am I correct I need to repeat this code and process, this time using the hook you gave
quform_entry_pre_process_#
for entries to be editable when value is outside range?- This reply was modified 6 years, 9 months ago by
katw. Reason: Solution and query on edit view
katw
ParticipantMakes sense.
Suggest adding a note to the docs (getting-form-values-data-types) under “Get a single form value (for safe use in HTML)” saying NOT to use this method when used in conjunction with
quform_get_value_html
hook. - AuthorPosts