[katw]

Thanks for confirming. Close ticket

[katw]

Oh ok, sorry if this was the case.

Consider it fixed then 😉

Apologies. Close ticket

• This reply was modified 6 years, 4 months ago by katw.

[katw]

Hi Ally,

Just following up to see if you have had a chance to read above.

I don’t need you to write anything (my job); what I do need is confirmation on your algorithm for generating radio button option IDENTIFIERS.

If I create my own unique identifier and keep your prefix “quform_2_81_” and trailing suffix “_#” will everything BIND okay?

So my thinking is:

I populate the “######” part of the <input id="quform_2_81_######_1" ....> with my own 6 character unique alphanumeric code for EACH auto-generated RADIO GROUP/SET. And I should be okay.

Yes?

[katw]

Hi @emorenopr.

Saw your post and thought I could help out.

A small CSS style change will do what you want.

If you are unsure how or what to do; I can help. Can you share link to the form so I can see buttons/code and give you complete answer?

Cheers

Kat

[katw]

I have put in new style fixes to solve the problem. I will temp disable these.

Test form.

The form is work in progress (so be kind). The easiest way to see fault is:

1. Ignore contact details block.
2. Choose FEEDBACK FOR: WEBSITE
3. Choose: Reporting issue
4. Scroll down see buttons under TECHNICAL DATA

[katw]

Many thanks Ally; had come to same conclusion myself 😉

Will give your suggestion a try.

Close ticket

[katw]

Would the order of loading (queuing) JS work out like this?

1. Quform Plugin operational JS
2. Quform Global Settings Custom JS
3. quform_pre_display hook JS enqueued code

Or is 2 and 3 swapped?

Concerned about load order.

[katw]

What about the CSS?

[katw]

Super thanks for clarifying.

[katw]

Nice idea, thanks.

[katw]

Hi Ally,

Does the date picker know about the range Min and Max set in field settings?

As the need to hide and show the arrow is based on what is {today’s date}.

Next year it will be valid to show a previous year arrow.

And a next year arrow will also be valid next year when the user pages backwards.

So hiding it without programming logic embedded will be a short term fix.

[katw]

Hi Ally,

It isn’t happening at the moment. So park it on the back-burner.

It now suggests a conflict and I need to watch for the conditions in which this happens.

I am aware a couple of plugins are using SELECT2 JS library (including yourself) and wonder if the menu that’s getting clipped is utilising Select2?

If so, I will watch out and see if I can give you any info; at least to help you for any future reports.

[katw]

Hi Ally,

Will see if still happening. Thanks for looking into it from your end.

Kat

[katw]

Worked like a treat. Thanks Ally.

Close ticket

[katw]

I have 100% confirmed it is the assumed $mailer using PHPmail for email sending that is the issue.

How do I modify the hook for $mailer = ZOHO mail?

Thanks

Kat

[Author]

Posts