Show Up Strong

So, how do we fix the duplicate error and failing CWVs for that?

Thank you @rsobczak for showing me where to find the old version and for your response.

Thank you @thaikolja for this great plugin and for fixing it so quickly. Everything seems to be working fine again.

I love this plugin and I completely understand it’s hard to make sure everything works perfectly, especially if this isn’t your full-time business/job. I appreciate your rapid response to the problem.

– We’re not requiring people register to make a purchase.
– I removed the user specific API’s.
– No caching for the plugin pages.
– Whitelisted certain things for the app to not be blocked by the firewall.
– Made sure the IPN call to the site was working and valid (that was directing to a 404 error page).
But I think the only real issue was the .biz vs .com

There was a slight error in the registered email address with PayPal even though they said it was the correct email address. It was .biz not .com. As soon as I found the error and corrected that, everything worked.

resoloved

Whoohoo! Thank you, it worked.

This is what’s in the .htaccess file

‘rewriteengine on

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
# Wordfence WAF
<Files “.user.ini”>
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
Order deny,allow
Deny from all
</IfModule>
</Files>
# END Wordfence WAF’

I’m still having issues with a backdoor somewhere, but I think this is solved for now. Thank you wfasa.

I think if got the .htaccess file cleaned out. Thank you for your help!

wfasa,

Thank you for the information. After my last scan, Wordfence no longer showed I have a problem. I’ve set up a premium SSL, in hope of not getting hacked again. I have my settings on High Sensitivity at all times, as my site seems to get attacked more than any business owner I know.

As far as manually checking those files, I have no idea how to do that.

Hi mountainguy2, it seems to be working to block any ip attempting to hit it. I’m still getting hit every three minutes with login attempts, but that part is working now. I did use the * wildcard.

Thank you! Do I need to put the *wildcard in front of it?

Do you know anything about the “?wordfence_logHuman…” hits? I’m getting a bunch of those too.

It’s a work in progress… your help saved me a lot of time and frustration. Thanks again.

Thank you! It worked perfectly.

Thank you for your responses. I ended up changing the themes stylesheet to get it to hide the title. I know that’s not the best thing to do, but since nothing else worked, I took a chance. I’ll try asking solo stream (the themes developer) for help, but it looks like the purchase of their themes don’t come with help (lesson learned).