[katw]

Entries List view – add setting to allow the display of additional data columns

Add ability to filter list by date range and view status

Add ability to “click column name” and sort ascending/descending

Add ability to “group by” IP number, user fields like email, phone

Thanks

[katw]

The forums are like a knowledge base and we could find previous answers that were relevant if we had better ways of filtering and finding tickets.

Could you add sub topic for QuForm 1 and QuForm 2 versions?

Could ticket state be used as a view/filter state eg Search tickets open, search tickets closed

Could you add tag categories so tickets could be classified by the user and used in search:

– validation
– data export
– entry view
– hooks
– email
– confirmation email
– popup form
etc

If we had these extra options we could browse the forums and find hints we could use.

[katw]

Hi, I did the same thing in my form. But I used checkboxes for “contact by” choice.

Add an email field and a phone number field. Set both to REQUIRED.

Now use the conditional logic option on each to hide/show these fields according to the users menu choice.

I didn’t use a popup menu but the approach should be the same.

The nice thing about the conditional logic, it handles the required and knows that if a field isn’t visible the required rule doesn’t apply.

Hope that helps a little

[katw]

That’s great re:update.

When you say JS do you mean toggling CSS display.none; or actually JQuery hide();?

[katw]

Add more informative alert message for session timeout in QuForm Edit.

“NONCE_CHECK_FAILED” –> Sorry, can’t save changes, session timed out

Also need to prevent lost work with timeouts.

Can we have a session count-down visible or a way to change session time?

[katw]

1. Hidden fields with CONDITIONAL LOGIC

2. New hook for custom validators to allow validation of empty fields

3. Customisable entry view, so you can add layout groups, columns and drag and drop fields, insert HTML blocks for instructions and custom presentation etc.

Basically reusing the form builder but in READ ONLY FIELD view…

4. Custom CSS and Custom JS field ALSO at form level (so code unique to a single form doesn’t get loaded with all forms)

5. Expanded conditional logic that also allows sub-levels and complex AND OR groupings, and set and get of field values

6. More filters like Uppercase, Titlecase, Sentence case, currency, add prefix, add suffix

Thanks

[katw]

Fantastic, I will follow that same format to build a title case filter too.

Thanks again.

CLOSE TICKET

[katw]

CLOSE TICKET

[katw]

Okay thanks.

CLOSE TICKET

[katw]

Thanks so much, you are a legend.

CLOSE TICKET

[katw]

Thanks Ally.

The more frustrated I got with the validator not functioning the more I started doubting my understanding of getElement and getValue.

I was on right track at start but didn’t know empty field aborted the validation exercise, so got myself tied in knots.

Thanks for the extra info.

CLOSE TICKET

[katw]

That’s a great solution… easier than exposing QuForms array of errors on front-end.

Thanks heaps!

Might I suggest putting this tip on the how-to page for WP DEBUG mode… it may help another person.

CLOSE TICKET with Thanks

[katw]

Does the addValidator function hold its state? persist after validation? Or reset?

As I need it to apply for that validation action only and reset ready for next ‘try’ at validation.

The user may after validation fail do change different in the form thereby changing the ‘required’ condition requirement.

Just need to know if I must reset validation … removeValidator(‘required’) then test if it’s needed.

Thanks

• This reply was modified 6 years, 11 months ago by katw. Reason: Wanted to explain purpose of question better

[katw]

I am struggling with using the ‘quform_pre_validate_1’ hook.

I can’t seem to access values in a hidden field (ID 1_62).

The value in this field will dictate whether I remove or add the ‘required’ validator.

I have tried using:

$errorValue = $form->getElement('quform_1_62'); 

if ($errorValue <>0) {
    $form->getElement('quform_1_4')->addValidator('required');
} else {
    $form->getElement('quform_1_4')->removeValidator('required');
}

AND

`$form = $element->getForm();
$errorValue = $form->getValue(‘quform_1_62’);

if ($errorValue <>0) {
$form->getElement(‘quform_1_4’)->addValidator(‘required’);
} else {
$form->getElement(‘quform_1_4’)->removeValidator(‘required’);
}`

BTW the quform_1_4 element is a radio button group.

quform_1_62 is a hidden field; one I need to check the value to determine if required is needed for the radio group.

General Questions:
———————-

Is the getElement(reference name) different when handling radio button groups?

Do I need to convert the hidden field $errorValue to a number before comparing?

Why do custom validators use $form->getValue but pre_validate hooks use $form->getElement?

• This reply was modified 6 years, 11 months ago by katw. Reason: Tried to get second code block to show as code, but not working

[katw]

To re-enable the validator for the field do I reverse the code like this?

$form->getElement('quform_1_4')->addValidator('required');

[Author]

Posts