Jelena

Since we haven’t heard from you in over 4 days, I assume that it’s sorted out so I’ll go ahead and close this thread for now. If you need any further help, feel free to reopen the conversation.

Thanks.

Hi,

Sorry to hear you’re facing issues with that. Dealing with comment spam can definitely be a hassle.

We recommend checking out Shield’s “SPAM Protection” docs and setting up the options:
https://help.getshieldsecurity.com/article/257-introduction-to-the-comments-spam-protection-feature

Also, it would be good to go though this guide on stopping comment spam:
https://getshieldsecurity.com/blog/effective-tips-on-stopping-comment-spam-on-your-wordpress-website/

Hope you find this helpful in some way.

Hi Joseph,

Since we haven’t heard from you in over 3 days, I’ll assume everything is sorted and close this thread. If that’s not the case, you’re welcome to reopen the conversation.

Jelena

Hi Joseph,

Sorry to hear that.

Since their IP is whitelisted, they shouldn’t be blocked by Shield at all. For whitelisted IP addresses, it’s as if the entire plugin is turned off, meaning there are no restrictions for users associated with that IP whatsoever.

Make sure their IP address is accurate and not changing—confirm they are not attempting to log in from a different IP address.

The only Shield feature that displays a “404 Not Found” message is the “Hide WP Login & Admin Page” feature:
https://help.getshieldsecurity.com/category/284-hide-wp-login-page

For example, if your client’s IP is whitelisted and they try to load the renamed login URL, they’ll get a 404 error. However, this feature will not trigger Shield’s blocking offenses—they won’t be blocked. You can disable this feature if needed.

However, to find out why exactly the blocking is happening, best thing to do is checking the WP Activity Log and use the IP Address filter box at the top of the table to filter by the blocked IP address. You can log into the site and ask your client to reproduce the block so you can immediately check the Activity Log. If in any way their IP address is changing, ask them to visit this page and provide to you IP address printed there:
https://getshieldsecurity.com/my-ip/

The log will show all activities for that IP and the reason it was blocked. Based on this information, you can adjust Shield settings to prevent future blocks. If you’re unsure how to interpret any log entries, you may use this Glossary here.

You may also want to temporarily disable page caching (either plugin or system) and suggest your client clear their browser cache and cookies before retrying.

Hope this helps.

Hi,

It’s been a week since we last heard from you. It seems like things are sorted out, so I’ll go ahead and close this thread. If that’s not the case or if you have more questions, feel free to continue the conversation.

Thanks.

Hi,

You won’t be locked out. These features will be disabled once the plugin is deactivated, and there’s no need to restore settings before deactivating.

Regarding the error, it may be caused by missing or corrupted Shield files. You can try reinstalling it from a fresh .zip file. Download it here:
https://www.ads-software.com/plugins/wp-simple-firewall/

To reinstall, first deactivate and delete Shield from your WP site’s admin area (Plugins page). Then, install it again using the downloaded .zip file and activate it.
(when you delete Shield, all your previously saved settings will remain intact-stored in the database.)

Hope this helps.

Hi,

If you deactivate Shield, it shouldn’t cause any errors or break your website. The plugin is designed to be safely deactivated without affecting your site’s core functionality.

Any changes made through Shield, such as security protections or configurations (e.g., firewall rules, login protection), will be automatically disabled when the plugin is turned off and re-enabled when you reactivate it.

You don’t need to manually revert any changes made through the plugin before deactivating it. Once you reactivate Shield, all your settings will remain intact, and the protections will resume as they were before.

Hope this helps.

@dleigh Thanks so much for following up again. Keep us posted if/when you hear back from them.

And absolutely no worries about the delay – we’re grateful for everything you’re doing to help. ??

@dleigh Just a quick reminder — have you had a chance to ask the MapSVG developer if they can provide the specific CSS selectors from our styles that are causing the issue, please? We’re about to release a patch and would like to address this if necessary.

Many thanks in advance.

Hi,

These are just PHP Deprecated notices and cause no harm or actual errors on your site. This is just an artifact from support a large range of PHP versions and ensuring there’s a compatible library.

You probably shouldn’t be logging these on a production site. The best thing you can do here is configuring your PHP logging to not log Deprecation notices and here’s how to do that:
https://stackoverflow.com/questions/5628148/disable-e-deprecated-in-php-error-log#answer-5651783

We’ll also definitely review them and try to eliminate them for future releases.

If you’re getting other types of errors aside from deprecated ones, feel free to share them.

Thanks.

@jharkhandlabofficialyt , here’s the link to post it:
https://www.ads-software.com/support/forum/miscellaneous/#new-topic-0

Hi,

It’s been a few days since we last heard from you, so I’ll go ahead and close this thread.
You’re welcome to reopen it anytime if you need further help.

Thanks,

Jelena

Hi,

Sorry to hear about the troubles you are having.

Shield will alert you when files get modified or new files are added (not part of your original core, plugin, theme installation files) and can keep repairing modified files automatically for you to ensure that it doesn’t contain any malicious code any longer.

We go into the all details in the Shield’s scans guide here.
(Malware, and Vulnerabilities scans are available for premium members only)

Please note that, due to the conditions set on the www.ads-software.com forums, we can’t discuss premium options here. But you can get quick help and advice from the Shield community by joining our Facebook group here. Or, contact us directly here.

So Shield can help but to stop malware from recurring, you’ll need to find the source of the problem. Malicious code can get in even on the server-side. Or, maybe this malvertising is in your theme files, e.g., ‘footer.php’ (just guessing).

Security, unfortunately, is an ongoing process and requires us to audit our sites regularly and to pay close attention to alerts sent from Shield. Shield will identify the issues as they arise and provide the mechanism to lock down a site and keep it as secure as possible, but often it can require more in-depth investigation to resolve the issue.

If you’ve removed this malware from your WordPress site but it keeps reappearing, it indicates that there might be an underlying issue or vulnerability that needs to be addressed. You’ll need to identify the source of reinfection and how this malware gets in.

Dealing with recurring infections can be challenging but it’s not impossible to do so. Here are some steps we highly recommend you to take to address the issue:

Security Audit: https://getshieldsecurity.com/blog/run-wordpress-security-audit/
27 Vulnerabilities: https://getshieldsecurity.com/blog/wordpress-security-vulnerabilities/

I understand there’s quite a bit to go through, but please follow the guides above one step at a time.

Jelena

Just a quick update for anyone who might experience the same issue:
it was a corrupted .htaccess file from another source and it’s always good to test temporarily removing your .htaccess files when you’re experiencing critical errors to eliminate it as a source of the problem.

@shivasirons , thanks again for reporting back. ??

Hi,

We are sorry but, by the terms of this forum, we can’t offer support for our premium members through this channel.

We opened a support ticket for you (#5462). Email is sent to your purchase email address. Please respond when you get a chance.

Thanks in advance and sorry for the troubles.

Jelena