Jared Atchison

@jdembowski Users who encounter complex problems that will likely require a lot of back and forth communication we ask to reach out to go through our ticketing system, to keep the process efficient. We have a full support team monitoring and working with those tickets, as compared as on www.remarpro.com where we provided limited support and are not able to monitor/respond as quickly ??

Hey @adamkws,

Sorry to hear you ran into trouble!

We’ve had over 1M users upgrade to WPForms 1.5.9 since last week, and by most accounts this have gone smoothly and as expected.

We have seen a few users encounter issues, which needs to be independently investigated, and we are more than happy to help with.

When you get a chance, please head over to https://wpforms.com/contact/, click “Complete a Form”, and submit.

In your message, reference this thread/URL, we’ll be on the look out for it!

This way we’ll be able to get more information from you and work towards resolving this.

Thanks!

Happy to clarify!

First, I’ll say these tables are intentional, please do not delete.

In WPForms 1.5.9 we introduced “background processes”, also known as asynchronous tasks. To do this, we leverage the Action Scheduler library, which is maintained by Automattic and is also used in WooCommerce.

https://actionscheduler.org/
https://github.com/woocommerce/action-scheduler/

This library allows us to run processes in the background and speed up form processing.

Currently we use this for sending form notification emails. So when a user submits a form, the emails will send in the background, instead of the form processing waiting the for the emails to send. In the future we’ll be using this library more to speed things up further!

The database tables you are seeing are installed by Action Scheduler. So they are 100% safe and should not be removed.

Hope that helps!

Hey @hurikhan,

Sorry to hear you ran into trouble. We definitely want to investigate this for you.

When you get a chance, please head over to https://wpforms.com/contact/, click “Complete a Form”, and submit.

In your message, reference this thread/URL, we’ll be on the look out for it!

This way we’ll be able to get more information from you and work towards resolving this.

Thanks!

We target 4-6 week “major” release cycle.

So this means next release should be second half of Feb.

However if critical bugs/issues come up, we’ll release a minor point release before then.

Next release will have this fix, regardless if major or minor release.

Hope that helps.

Sorry about that!

The good news is this was fixed on Monday. However, unfortunately this was after the latest release was finalized.

But this fix will 100% be included in the next update, regardless if it is a minor or major release.

Hey moraima4,

Thanks for reaching out – very sorry about that. As of this afternoon, version 1.5.8.2 is available and should fix that error ??

Have a good one!

It’s definitely something we need to improve on our end, because what you experienced is not an uncommon issue. We probably will end up trying to detect the “from address” set in notifications, and warn users if it doesn’t match the site domain or email configured in the SMTP settings.

One thing we’ve seen is when the “from email” isn’t properly setup, the email is silently discarded on the mail server end, meaning if you log the return on wp_mail() it still returns true despite the email never being delivered (not even going to spam folder).

Hey @afragen,

Thanks for following up, I appreciate it. If there’s anything else that comes up just let me know! (jaredatch is PostStatus Slack).

Thanks!

Sorry about that!

When you get a chance, can you let us know what specifically you edited (inside class-frontend.php) or what the JS errors were?

We have no plans to add support for reCAPTCHA v3 right now.

The reason is because it’s a frustrating and confusing experience for users.

They get assigned a spam score which is compared to a threshold, but no way to prove they are not spam.

reCAPTCHA v3 does do a good job in keeping the spammers in check, but the trade off us it catches real users in the process with false positives. I have first hand experience with this as other plugins I’m involved with (WPForms) have support for v3.

For this reason it is not something we are planning right now.

• This reply was modified 5 years, 3 months ago by Jared Atchison.

Thank you @mgtri for reporting back with your findings, very much appreciated!

Looks like it! ??

When you get a chance please email [email protected] and reference this page. We’ll be able to track down your license and help get this figured out!

@jkwalz – thanks for the follow up! I suspect maybe you are using a different plugin and not WPForms?

File Upload functionality is only available to paid license holders. In addition to this, we do not currently support email notification attachments with files that are uploaded.

I’d first start by logging in to your SharedCount account area and looking at your API usage.

Awhile back they lowered the quotas on the free plan. If the quota is exceeded it might be preventing counts from being shown for that specific request.