ewedige

I’ll have to play around with that other plug in this weekend. Looks like it’s a “GoDaddy” issue. They do lots of stuff good (I’ve had great luck with their tech support), but once in a while….

Thank you for the help. I’ll let you know how it goes. I found that other plugin when looking for yours, but yours looked like the more secure version.

My web host is GoDaddy. Here’s the info from the server tab:

OS: Linux p3plcpnl0245.prod.phx3.secureserver.net 2.6.32-673.8.1.lve1.4.3.el6.x86_64 #1 SMP Wed Feb 10 08:57:30 EST 2016 x86_64
PHP version: 5.4.43
WordPress version: 4.5.2
WordPress multisite: No
openssl: Available
allow_url_fopen: Enabled
stream_socket_client: Available
fsockopen: Available

I did, but when looking through my setup I didn’t see anything stick out. I also looked for a similar error in the doc and searched on the internet and haven’s found anyone having a similar issue.

Thanks for getting back to me. I checked the version of PHP my host is using and it is 5.4 so it’s more recent than the 5.3 that you’re saying it needs.

I’m using version 2.3.25 of your plugin and I’m still having the issue of it not being able to open the file.

Thanks.
Eric

I had the same issue (the captcha not showing) and also wasn’t getting it to redirect to a confirmation page. I tried your beta release and it fixed both issues. Thanks.
https://www.mendotafreeze.com

I have a hard time considering this to be resolved when the fix listed is to edit your theme’s function.php file to add a new function. Editing the theme’s files to make a plug-in work doesn’t sound right to me no matter how you sell it. You change your theme, the plug-in stops working. You upgrade your theme, the plug-in stops working. Neither of those things should happen. You should never have to edit the theme to make a plug-in work, especially an for a plug-in that is in no way connected to the theme.

I would like to see the fix you described added into your existing plug-in. It controls the functionality of this plug-in so it should be included in the plug-in, not in a separate plug-in as you mentioned you were thinking of doing.

Please make the fix so this included in a future update to your current plug-in. If needed, make it an option, but make it self contained.

I did use your fix, but created a separate plug-in with your one line of code in it so that any updates or changes to my theme don’t stop the plug-in from working. This is not ideal in anyway, but is much better than your suggestion of editing the theme.

I’ve been looking for this too. I’d like to third the request.