[diegocanal]

Hi Ally,

Would you be so kind as to pass me the piece of code (and where to place it) to fix this? so I do not have to wait until the next update, you know…some times it takes quite a while.

Thanks!

[diegocanal]

Hi Ally,

You hit the nail on the head, exactly, my request was for Checkboxes and Radio Buttons (Multiple Choice) but I have taken a look and there are others, so the list ends up like this:

• Checkboxes
• Radio Buttons (Multiple Choice)
• Date
• Time
• File Upload
• reCAPTCHA

Thank you!

Regards
Diego

[diegocanal]

Hi Félix,

I will give it a try sometime but I do not think I am going to use it now as I tend to use as little Javascript as possible, for performance reasons.

Thank’s for the tip!

Regards
Diego

[diegocanal]

Hi Ally,

I really appreciate your time. The code you have provided works perfectly on my side, using it along with the previous one has given me a complete solution for both, the notification and autoreply emails.

I have tuned up the code a bit in order to customize the output of the subject and body to fulfil my requirements, so now it works exactly as it used to except for the fact everything goes out through wp_mail, exactly what I wanted.

Being able to use wp_mail allows me to employ “Postman SMTP Mailer/Email Log” plugin, thus I can take advantage of Auth 2.0 authentication with the Google Apps Gmail API, giving me peace of mind regarding my dmarc implementation –having all my autoreply emails reaching their destination–.

Ally, thank you very very much again, your support is awesome, just as good as the quality of your work (product).

Best regards,
Diego

[diegocanal]

Hi Ally,

Sorry for the late response.

Thank you very much for the piece of code provided. It works fine for the notification email but it does not work for the autoreply email…would it be too much to ask you for a similar piece of code to accomplish that (autoreply email through wp_mail)?

Thanks!

Regards
Diego

[diegocanal]

Hi,

I was wondering if you would be so kind as to provide us with some custom code to allow all our forms to use the WordPress API wp_mail to send mail, until you include this option in a future release.

Thanks!

Best regards,

[diegocanal]

Hi Ally,

Thanks for the improved piece of code! I appreciate it.

I hope a client side validation functionality will be added to Quform sometime in the future, it would be very interesting from a UX perspective.

I really appreciate your help.

Regards
Diego

[diegocanal]

Hi Ally,

Thank you very much for such a thoughtful response. I will try to implement a validation library or jQuery. In the meantime I may use your workaround.

I really appreciate your help.

Thanks!

Regards,
Diego

[diegocanal]

Thanks Ally!

Regards,
Diego

[diegocanal]

Hi,

That is what I have been doing (using the Text Widget + shortcode) so far 🙂 but it has a drawback in my case so that is why I wanted this solution.

The point is that I use the form in a sidebar and make it sticky on scroll down (using a jQuery script). To make it work I must init the script using the id or class of the parent of the widget, no mater if it is a Text Widget or a Quform Widget. Because my Text Widgets are nested whithin another div with a unique ID (I am not sure if that is done by WP or by my theme), for example:

	
<div class="custom-sidebar widget_text" id="text-43" style="">
	<div class="textwidget">
	........our iphorm code or shortcode
	</div>
</div>

…up till now I’ve been using the parent’s element ID (on the example above it would have been text-43), but I has not been happy with that solution because that is a unique id to that particular Text Widget – also notice that using the class was not an option because I could have more than just one Text Widget in the same sidebar – so I’ve been forced to extract that ID in every page in order to use it in the init of the sticky script.

With the piece of code you’ve just provided (BTW, I don’t know if on purpose but you put class instead of ID) I can use the iphorm-widget-wrapper ID, both, for the anchor link and the init of the sticky script, so now I am a happy man 🙂

I really appreciate your help on this matter.

Thank you!

Regards,
—
Diego

• This reply was modified 9 years, 9 months ago by diegocanal.

[diegocanal]

Hi Ally,

I am not trying to have several html elements with the same ID on the same page, actually, I never have more than one form on the same page. Please, notice that on my previous post I said:

Now I have, in different pages, quform widgets like:

On the other hand, I am afraid the class iphorm-widget does not solve it. The point is that I need the wrapping element with an ID, around the whole iphorm widget, because I need to have an anchor link pointing to it. Also I cannot use the specific ID of a given form (for example: iphorm-widget-10) because I am building a page template (php) that is going to be used for diferent pages, each of them with a dfferent form in it.

The solution you’ve provided solves it, but with an undesirable side effect, it replaces the specific ID of the widget (for example: replacing iphorm-widget-10 with iphorm-widget-wrapper), because of that we loose especificity to style forms on a per form basis (for example: #iphorm-widget-10 .iphorm-outer {…)

The definitive solution would be what I asked for on my first post – injecting/adding a new div, with a general ID, (iphorm-widget-wrapper) wrapping around the whole iphorm widget.

In summary, instead of getting (with your previous piece of code):

<div class="custom-sidebar gdl-divider iphorm-widget" id="iphorm-widget-wrapper">
	...
	...
</div>

The ideal output would be:

<div id="iphorm-widget-wrapper">
    <div class="custom-sidebar gdl-divider iphorm-widget" id="iphorm-widget-10">
    	...
    	...
    </div>
</div>

IMO this would be a great addition to the pluging. It might be an option that could be toggled on and off or that were toggled off when there are more than one forms on the same page.

I would be very grateful if you could provide the piece of code to achive that.

Thank you very much for your kind attention.

Regards,
—
Diego

• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.
• This reply was modified 9 years, 9 months ago by diegocanal.

[diegocanal]

Hi Ally,

I was wondering if you would be so kind as to update the file jquery.smooth-scroll.min.js in Quform to its last version.

As you provably know already, this is a very robust plugin, with a good and helpful developer behind it and I am sure the update will not cause you any trouble.

I am using the last version (1.5.6) in some projects and it is working flawlessly, you are still using version 1.4.9.

BTW, I added a few more strings to the Quform Spanish translation (just 3% 🙂 sorry). I have tried to attach the files here with no luck, please let me know how I can send them to you.

Regards,

• This reply was modified 9 years, 10 months ago by diegocanal.

[diegocanal]

Hi Ally,

It works perfect.

Thanks!

Regards,

Diego

[diegocanal]

Hey Ally,

My host has confirmed that the “Disk quota exceeded (122)” error was caused by a maintenance task they run that night. It prevented the plugin from accessing the root folder where it was the temporary folder. I have plenty of free space on my disk, it was just that blockage.

Anyway, this issue has been caused by my server. This thread can be closed.

Thank you for your assistance. It has been very kind of you.

Regards,
Diego

[diegocanal]

Hi Ally,

It has already been solved by my host, they have given me the following explanation:

This incidence is due to that it has not been defined a temporary directory for the plugin. We have performed the following actions:

– Create a directory within the installation of wordpress, e.g. “tmp1”

– Give 777 permissions to that directory

– In wp -config.php we have added this line:

session_save_path ( ' tmp1 ');

These sites have been running with Quform for years with no issues. Could you please think of what could have caused this issue in all these sites simultaneously?

Thanks.

Best Regards,

[Author]

Posts