wpissuesreports
Forum Replies Created
-
You are deleting every comment. You got sworn at because you are being unreasonable and irrational.
The plugin was spamming users with Pro ads on every back end admin page. My site was not hacked.
Jan Dembowski is being abusive. He is also hiding information.
I just fixed their plugin for them. Next time I won’t tell them what they did wrong. Ther plugin can stay broken.
Those two slugs are not allowed. A slug cannot contain the word wordpress or the name of another product. Both are in violation.
Yes, I am aware that wordpress-seo was grandfathered before this rule was implemented.
So go ahead, keep trying to make me look bad, and you can do it, because you can delete everything I say and then quote it out of context.
You fool no one. Get over yourselves.
Note the wordpress-seo plugin slug directory that you left behind breaks the WordPress Site Health Check. (presumably because two plugins are trying to be the same plugin) Now that I have identified your leftover directory with a plugin of the same name in a different slug, my Site Health Check works again.
Looks like one of your updates did not remove the wordpress-seo (illegal name) directory when you changed the plugin slug. Since the plugin code has been in that directory slug for over 10 years, I just assumed it was still there. (And the new spam code was of course not there)
I have discovered that Yoast SEO now resides in a directory called google-analytics-for-wordpress (also an illegal name, though it is clear the rules only apply to some developers).
I was able to find your spam code and remove it.
I suggest you cleanup your old slug folders before a vulnerability is found in the code that was left behind.
Seems that audit has missed a few things.