Jared Atchison

Also, this detection/notice can be disabled entirely if needed.

WP Mail SMTP > Settings > Misc > “Hide Email Delivery Errors” <— check that and save ??

Hey @elxr,

Thanks for reaching out!

The entry exporting issue should be fix in v1.6.2.1 which will go out tomorrow (Friday). Very sorry about that.

As a Pro customer if you have any other questions feel free to put in a support ticket directly through your WPForms account dashboard.

Thanks ??

@afragen – As Gregor mentioned, appreciate the shim. This is definitely on or radar!

Hey @podwabbit,

Very sorry for the trouble. Obviously that’s not what we want to hear or ever want a user to encounter.

Would you be able to provide the error/details behind the fatal error?

I’d certainly like to get to the bottom of this for you and am here to help.

Please let me know!

Thanks,
Jared

Hey @wpfan1000,

Apologize for the trouble you encountered!

It’s hard to say exactly what went wrong here, but the details you provided (thanks for that!) lead me to believe the upgrade didn’t download all the files or something along those lines. I saw this because those errors seem like files are missing which should obviously never be the case.

It’s possible there was a hiccup in the upgrade process, though that rarely happens, which is why I’m puzzled.

I would try deactivating and deleting WPForms from your site (all your forms and settings will stay intact) and then reinstalling/activating. This will force a “fresh” copy of WPForms Lite to be downloaded, so if any files were missing as part of the upgrade process, those issues would get resolved.

Please let us know!

Hey @power2009,

Thanks for the feedback and I’m sorry about that. This is something we’re obviously going to look into promptly ??

Have a great weekend!

@judemarriott @webniche – thank you both for the updates, I appreciate it. I’m very sorry you weren’t able to get things working.

Would you mind letting me know what plugin/solution you moved to that is working for you? This would allow us to investigate and see what they are doing differently and improve on our end.

Thanks again!

Hey @judemarriott – sorry for the trouble!

With Bluehost, there may be some setup needed within the account panel first, you might have done that already, but wanted to point that out just in case.

Generally, the settings that others appear to have good results with are:
Port: 465
Encryption: SSL
Authentication: on

Check out the links below, they provide a more in-depth walk through.

https://www.isitwp.com/set-configure-smtp-wordpress/
https://www.scottcole.net/bluehost-wordpress-smtp/

Let us know if that helps ??

Hey @awaissmith,

Thanks for reaching out. Perhaps you were able to get the issue resolved? I visited the link you included and everything appears as I would expect ??

Let us know.

Thanks!

Jared

Hey @crestacreclinic,

Hope you had a good weened and thank you for the update. If you’d like to change or remove the review, that’s cool.

But most importantly we do really value the feedback and I’ve made a note that we need to revisit how we can better communicate how and what the phone field does.

Thanks again for the insight ??

Hey @crestacreclinic,

I appreciate the honest feedback.

I suspect we don’t do a very good job providing more details about our phone field and how it works.

Unlike other platforms, our phone field is _actually_ “fancy” ??

https://a.cl.ly/mXuBYPr5
https://a.cl.ly/JrubOnD0

By default, our phone field use geolocation to detect the visitors general region and adjust the suggested phone format as well as the country code which is stored with the phone number. It’s super neat and we’re really proud of this feature and our customers really dig it.

The geolocation is powered by our own geolocation API we maintain and update, which is why this is a paid feature.

(Side note, “fancy” fields are available to all WPForms paid licenses, including Basic)

If you want a more simple approach to collecting phone numbers with WPForms, you can use the “Numbers” field or the Single Line Text field in combination with our input mask (https://wpforms.com/docs/how-to-use-custom-input-masks/) which is similar to what others provide.

Can you let me know if that helps shed some light on why things are the way they are?

• This reply was modified 4 years, 10 months ago by Jared Atchison.

Thanks @crstauf – we’re going to take a look. Appreciate the details. We’ll follow up once we’ve done more digging.

@mstep Sure thing. I apologize for the trouble! It looks like a database table wasn’t correctly created.

I’m not sure if options.php is available in multisite. If it’s not you may need to use phpMyAdmin or similar to access the database.

As you mentioned, in multisite, there are different DB tables for each site, wp_x_ with X being the site ID.

So you’d want to search for “wpforms_version_lite” within the option table that corresponds to this site if you’re still having issues, and simply remove that option. This should trigger the database to be created.

Again, very sorry for the trouble. We have an update coming out in the next week or two, and we’re going to make sure and do more testing on multisite so this isn’t an issue.

• This reply was modified 4 years, 11 months ago by Jared Atchison.

Thanks for following up to confirm Alex, appreciate it. Again, sorry for the trouble. We’re going to work hard to make sure future updates are seamless as expected!

Hey @alexandreyev,

I apologize for the trouble. Thank you for providing details about the error you encountered.

We just released an update, WPForms Lite 1.5.9.5, which should fix the issue and get everything working as expected.

When you get a chance, please update and give it a go.

Again, very sorry about this!

Thanks,

Jared