Paul

I honestly have no idea why that would happen. You could try looking here and do as other have done and adjust how you implement your WP Cron scheduling. We call WordPress’ API to hook a cron, and if it doesn’t work, it’s likely something local that’s causing a problem. I couldn’t possibly say why a given cron hook doesn’t work.

Hi,

Shield tracks numerous core WP settings, such as your tagline (among other things). If your tagline is changing constantly, this is because you have a plugin/theme on there that is programmatically altering your tagline.

Why it’s doing that, is anyone’s guess, but something is doing it. But interestingly it’s not doing it for every WP load, only on some of them, which is why Shield detects it changing, constantly. You’ll want to find the source of the changes and determine why it’s doing that, and perhaps update the tagline of your site in your core WP Settings page to be the one you want.

To the question of compatibility, there’s no reason why Shield wouldn’t work with WP Optimise. As for running another security plugin alongside Shield, 1 security plugin doesn’t know what the other is doing, and we don’t support comparing 2x security plugins alongside each other. If you want to run 2, then you will need to take on the risk of that and potentially deal with any confusing or contradictory reports between the 2. We suggest you pick one and stick with that one.

Is there something you think is missing in Shield that you need from another plugin?

Thanks.

We’ve just published v20.0.10, so if you want to try upgrading and seeing if it helps, let me know. I cleaned a few styles up from the CSS in the admin area and maybe I caught the ones causing issues. If not, let us know what the dev from the other plugin reports back.

We load a limited set of styles in the WP Admin area, because we need to for certain items. Could you ask the developer to specify the CSS selectors in our style sheet that’s problematic, please? We’ll look at updating any styles for our next release.

Thanks.

We develop and release updates regularly, sometimes there are issues that pop up – it’s the nature of software development. We’ll have mitigation for this deprecation warning in our next release.

You may need to discuss this forum post with your host so that they configure your webhosting to not display errors. Either you need to do it, or your webhost needs to do it, or you’ll need to engage with someone with the know-how to make such changes.

What we outlined is standard practice on a WordPress site – never display errors/warnings on a public site. Coding is required because this is how WordPress sites operate.

Deprecated notifications are part of PHP, and you’ll see them in greater numbers when you run higher versions of PHP.

They aren’t errors, but just notices to say that in future versions of PHP, they will likely generate errors.

You shouldn’t be displaying PHP Deprecation notices on a live WordPress site. Deprecations don’t cause problems and they don’t impact your site in any way… unless you display them on the website. That output may interfere with other processes, such as sending headers/cookies, perhaps as you’re alluding to when you say it’s causing other “errors” on other pages.

The solution is to not display deprecation notices, or errors, on a public, live website. We have an article on our site that outlines steps you can take to prevent PHP notices being displayed. There are many resources for this sort of thing if you want to find alternatives or perhaps options for your particularly web hosting setup. Here are some:

• www.ads-software.com – set WP_DEBUG to false
• Stackexchange
• Reddit

I hope this helps.

Hi,

these are not relating to our plugin – I think you’ll need to post this on the general WP forum for support. I think you’ve mistakenly posted it here. Try posting again to general forums for support.

Thanks,

There is a REST API endpoint to initiate a scan, and also to get Scan results, but not to execute a file repair. It’s certainly something we can look at, however, though there would be certain limitations depending on the nature of the file that’s got a problem.

Hi,

Thanks for reaching out to us about this. What you say is correct, and it’s something we’re looking at as we’re refreshing our site in recent weeks. Thanks for raising this!

Due to the conditions set on the www.ads-software.com forums, we can’t discuss paid options here, but I’d be happy to discuss this further with you, and if necessary jump on a call to chat about it. The best way to start that conversation is directly with us over email support@ our primary domain (getshieldsecurity.com). Drop us a line there and I’ll get right back to you.

Thanks!

That’s a bit of a wild one, particularly with it only happening on your wifi. I honestly haven’t heard anything similar from any other members.

When they’re “forever” loading the frontend, can you switch on the console and see which assets are not getting loaded under the “network” tab? That might give a clue.

When loading the admin, can you do the same and see if you’re getting any signs under the network tab of what’s not loading.

Are there any server/PHP errors being logged?

For now the best bet is to find out what’s not getting loaded in the browser. Have you tried

• resetting your router?
• testing over a VPN?

Let us know what you find. Thanks!

Our Releases changelog is here: https://getshieldsecurity.com/changelog/

For each major release (linked to from within the changelog), there is a blog article that highlights the biggest changes, and an Upgrade Guide to detail what’s changed exactly.

The Autoupdates module was completely removed in v20, and 1 setting (Upgrade Delays) moved to another section.

Great to hear, thanks for reporting back and letting us know.

The only other thing I can suggest is when you click the link, there’s a conflict with another plugin or theme that causes an error and the action fails. We can’t reproduce the problem, so it’s likely something specific to your site. You could try disabling other plugins, not Shield and see if you can get it working until you can find the conflict.

As to giving up on Shield, if you feel that’s best for you and your site, we’ll be sorry to hear that. But we always say that our members should chose the solution that works best for you. If that’s not Shield, that’s unfortunate but perfectly okay.

If we didn’t improve Shield and evolve it, we’d be criticised by for not continuing to develop the service. We’re very far from being lost.

All the best!

Could you try reinstalling the Shield plugin, please? That file/class is present in the release ZIP, so if it’s saying there’s no such class, then I suspect WordPRess didn’t complete the latest upgrade process successful and it may not have copied all the files.