keith

OK. I wanted to make sure. I am using the plugin to make sure the email domain name matches the website domain so that the hosting’s email server won’t reject it. I just noticed it since it came up in the WordPress site health report and wanted to make sure something didn’t change.

any idea when this will be fixed? or should i go ahead and fix it so i don’t have to remove debug mode on a development instance.

it is all up to date. premium version (i sent a support email with no response yet).

all i am asking is it safe to delete the data by disabling the related featured.

you have to set the “from” email address to use an email address with the same domain name as the server. it is under the “advanced” fields under the email notification settings. the “to” email address has to be a different email address, such as your gmail address or another email address with the same domain name as the server. the “reply-to” email address can be set to the person’s email address submitting the form. you can also use tool like wp smtp mail to force the “from” email address and also test emails to make sure they aren’t bounced.

inline js was already disabled. i disabled inline css and minify excluded files. this seems to have fixed the problem.

yes, to be fair, fear all plugin updates. wordpress programmers are so underpaid for all the things that can go wrong.

no recaptcha. the opt-in checkbox and none of the hidden input fields have unique css ids.

i went ahead and changed our code to use only one form.

we were using 3 forms for mobile, tablet, and desktop in avada. the code was simple enough to use only one form. it only required adding media queries for one div. it has gone through several redesigns.

the forms and email address fields had unique css ids or classes, but they all had hidden input fields related to validation with the same css id. i believe this would cause the plugin’s jquery to check validation values using the first form instead of the form being submitted.

they should have grabbed the existing collation and used it. this type of software development is difficult when you are deploying to unknown environments. you really have to do some kind testing trial with several unknown environments.

the update did take about one minute per 1000 posts on an $80/month server.

i would imagine if you are updating several thousand posts, it would get you throttled on even a premium account of an economy shared web hosting plan, even with someone like siteground, inmotion, or a2hosting.

yoast should have used a single large custom sql query rather than running small individual queries for each post or used a larger page setting. it isn’t about memory in today’s world, it is all about all those connections to the database.

it seems to work on sites with free yoast that aren’t automatically updated. it seemed to work on a site with a premium version of yoast, though I was skeptical of the “smart” update, especially after another person said it would take 33 hours to complete the request, so i hid the notice on a website with 20k posts.

it breaks on sites with free yoast with automatic updates turned on by the cpanel app installer.

i wouldn’t sleep until i fixed a bug like this, knowing it is affecting millions of websites.

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

uninstalling yoast if the plugin author gives you 10 steps to fix their plugin

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

thank you

fixed problem. thank you.

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