Jelena
Forum Replies Created
-
Hi,
Thanks for sharing this with us.
The messages that start with this:
Deprecated: Return type of
These aren’t errors. They’re deprecation notices. You probably shouldn’t be logging these on a production site. They’re not a problem and they don’t cause other errors. You can ignore these completely.
Shield has some PHP libraries that give deprecation notices because we have to support PHP 7.2.5+. However, these deprecations will be removed in our next release.Regards,
Jelena
Okay, thanks for the update. 🙂
Hi,
Thanks for reporting this.
Can you just reload the Wizard page, please? It should load so you can use it normally.
In the meantime we’ll take a look and include a fix for our next release to prevent it from happening again.
Regards and sorry for the troubles,
Jelena
Hi Timi,
Just letting you know that this is a double thread and we are closing it.
We answered the original thread, here:
https://wordpress.org/support/topic/shield-plugin-related-entries-in-error-log/Regards,
Jelena
Hi,
Sorry to hear about the troubles you are having there… We are here to help, however we can.
You can automatically unblock (remove your IP from the block list) via FTP by using the ‘unblock’ file flag functionality, detailed here.
There are other auto-unblocking options too.
When you remove or re-install Shield, all your previously saved settings will be saved in a database, including Security Admin access PIN, which is a password that can be set by site admins only. Since you don’t remember your PIN, you got blocked again. This is because Shield is trying to protect your site from unauthorised access.
Instead of disabling or re-installing, best and the easiest way is using a forceoff method outlined here. This will keep Shield active allowing you to get back into your site. Once you are in, you can remove your IP from the block list, disable or update your Security Admin PIN – solve the block.
If you don’t know what’s triggering the block, in that case you can check your Activity Log. It’ll tell you why you’re getting blocked so you can tweak Shield settings to prevent it from happening again. We have a complete guide (steps) on this here:
I’m Blocked/Blacklisted By The Shield. How To Unblock And Prevent ThisHope this helps.
Jelena
Hi,
Since we haven’t received any update from you in the past 6 months, we are closing this thread.
Regards,
Jelena
Hi,
All entries for shield_mod_config_* belong to the Shield and can be safely deleted.
You can simply run an SQL delete on everything that looks like shield_mod_config_.Hi,
Thanks for your question.When you have logs for logged-in users excluded in the settings (Traffic Log > Traffic Logging Options >Logged-In Users option selected), log of the Home page request will not display for them. This is normal.
So, if you’re logged-in and then load your Home page, all you’ll see (as you mentioned) will be an ajax call.However, if you are not logged-in, Home page request logs will display normally, for example:
https://www.screencast.com/t/H3pcyYAOwV2There’s no need to log Home page request for the logged-in users but if you want to see this request too, you can uncheck “Logged-In Users” option from the list of logging exclusions and you’ll see something like this:
https://www.screencast.com/t/FOPmqf7kv8eJust note that, if you decide to go for it, the all requests for the logged-in users will be logged too.
Hope this helps.
Jelena
Thanks so much for sharing your thoughts with us.
Your suggestion is added on the list of feature suggestions and we’ll see what we can do about it.
Regards,
Jelena
Hi,
Thanks for reporting this and sorry for the troubles.
We’ve spotted the same and we have it fixed for the upcoming release.
Thanks for the update. Much appreciated.
Cheers! 🙂
Jelena
No problem, Achim. Happy to help.
Have a marvelous weekend too!
Hi Achim,
It could be, yes. Especially because we already know that Simply Schedule Appointments is conflicting.
If you have this plugin on your site, you can temp disable it but keep Shield enabled and test. If the error is gone, this is confirmation that that’s the plugin you’re looking for.
Also, regarding Simply Schedule Appointments, It looks that their squad is on it. We’ve received an update from one of the Shield members:
I have heard directly from the developer of Simply Schedule Appointments have updated their code to support the conflicting library. The fix will be out within the next week or two weeks. In the meantime, people can download the beta version if they want to try it out.
Regards and about the quick reply, no problem at all. 🙂
Jelena
Hi Achim,
Sorry to hear that…
Whenever you can’t access your site as the result of Shield, for any reason, best is to use a forceoff method outlined here.
You’re getting this error because there’s a plugin on your site using an older version of the PHP carbon library.
We discussed this error here:
https://wordpress.org/support/topic/possible-conflict-with-simply-schedule-appointments-plugin/The Carbon library that we’re using in Shield is fairly widely used and is likely used within another plugins. The version of the other plugin on your site is likely version 1.0 (deprecated and fairly old) and it’s conflicting with the version of Carbon within Shield (v2).
We’ve switched to PHP 7.2 minimum and also with a view to support PHP 8.2+… this required us to upgrade several of our PHP libraries, one of which was Carbon (the other was Monolog).
After numerous releases, we’ve made a significant change in how we load the Monolog library to prevent fatal errors, but this does mean that any sites with conflicting Monlog libraries will not be able to use Shield’s Activity Log or Traffic Log features. It was this, or allow sites to go offline with fatal errors.
This same change we made with Monolog can’t be applied to Carbon as it’s too deeply integrated into Shield. This means that if you have a site throwing errors relating to Carbon, then you can either:
1) Find and disable/replace the plugin with the conflicting Carbon library.
2) Disable Shield until an alternative plugin can be found to replace the conflict. Contact the dev of the plugin and ask them if they’d consider moving to Carbon v2.
3) Revert Shield to the 16.1.15 version
But again, you’ll need to push the conflicting plugin devs to update their PHP carbon library. Once they do that, you can upgrade Shield to the latest version normally.
4) Remove ShieldWe have little choice in this… in order to keep up with the changing PHP developments, we have to keep our libraries current. And this means that eventually there’s going to be a conflict somewhere. It’s better to support upcoming PHP versions such as 8.2 and above than to be permanently stuck with old and deprecated libraries. Not an easy choice…
Hope you find this helpful…
@gugaalves , that’s great, thanks! 🙂
For anyone reading this, as @karthost mentioned, at the moment best is to revert Shield to the previous v16.1.15 till the Events Calendar folks release a fix for this error.
When you revert, please ensure that you have the Shield plugin auto-update disabled, under the main Config menu > Auto Updates > Auto-Update Options > Auto Update Plugin > disabled.