dletell
Forum Replies Created
-
It looks like I’d have to pay first. I see that it says if it’s your bug you’d refund it, but I don’t rely on the plugin enough to justify the cost.
That being said I do see three other recent posts for the same issue. Though their issues manifest as the forms stalling and I don’t know if they dug into the debugger enough to generate error codes, I suspect the fact that they disabled mailer and it worked indicates to me that it’s a plugin glitch, perhaps related to pulling a depreciated version of PHPMailer.
It does not appear that adjusting any email setting solves this issue. The only surefire way to avoid this is deactivating the plugin entirely.
Thanks, I was able to use your information to figure out that the plugin UpiCRM – Lead Management and Contact Form DB for all forms.
was calling a PHPMailer, and deactivating it caused an error. I will reach out to them. Thanks!It is a custom server rather than a hosting package. There is no other SMTP program. It worked before 5.5 update.
Issuing an update does not solve the issue without FTP access because this error prevents access to the WordPress dashboard. Any users encountering this (myself included) would need FTP or cPanel access to either delete the plugin or manually update it.
- This reply was modified 4 years, 9 months ago by dletell.
You’d need FTP access or cPanel file access to delete the plugin and find a new one. That’s about all the support available from these new owners.
Forum: Plugins
In reply to: [W3 Total Cache] Gravity Form Conflict@vmarko This did fix the issue for me and Gravity Forms works properly now. Thanks!
Forum: Plugins
In reply to: [W3 Total Cache] Gravity Form ConflictForum: Plugins
In reply to: [W3 Total Cache] Gravity Form ConflictI am having the exact same issue since updating W3 Total Cache on all my sites. I have done the work listed above and isolated it to the Minify functionality.
Minify was previously set up to not minify the pages and scripts as listed above, but since the most recent update there are conflicts once again when Minify is turned on. Previously it worked without errors, but since updating a few days ago all Gravity Forms functionality is now disabled.
The only setting that directly affects whether Gravity Forms works or doesn’t work is HTML Minify Enabled/Disabled. Turning JS or CSS Minify on/off does not affect functionality. Even enabling or disabling the sub-items in that HTML category such as Inline CSS, Inline JS, and Line Break Removal has no effect on it.
Let me know what can be done to fix this. Thanks!
- This reply was modified 4 years, 11 months ago by dletell.
It is. Right now my current thought is to disable W3 Total Cache from running on the page. That plugin has caused problems on other forms before. I’ll let you know if I encounter any other instances of this happening. Thanks!
Yes that’s exactly what it is. Thanks so much! I’ll keep an eye on Apple to release a fix and see if any of those patches work in the meantime.
This appears to be an issue with AJAX as others have indicated similar issues when using AJAX. You can turn AJAX off and have forms reload new pages each time the user goes to the next page of a form, but the problem is that then if you have multiple pages per form the Recaptcha will load on each page of the form, and there’s a soft limit on the number of times the Recaptcha can be submitted before it starts to verify humanity. So, the end result is that the user isn’t prompted on page one, maybe page two, but by page three they’re going to start getting humanity verification prompts.
Hopefully the developers adjust their code to support AJAX.
Forum: Plugins
In reply to: [W3 Total Cache] 0.9.5 fail -> Replace it with 0.9.4.1Thank you so much! I got my client’s website back thanks to this tip. They’re running an older version of PHP, and their previous developer who set up the web host went AWOL, so I was in the process of getting them moved over. This helps greatly to have figured out the issue and get a download link from you.
Thanks again!
Forum: Plugins
In reply to: [Easy Testimonials] 2.0.5 update breaks websiteNo worries, working fine now. Thank you!