Paul

Hi, tthe Shield plugin only sends emails from the site, so if the site is offline, then it can’t send emails. What is nature of the emails? Can you share some of its content?

Thanks.

When a malicious IP triggers any security event on your site, the event that was triggered, the time it was triggered, along with that IP address, are sent to CrowdSec. That’s completely all the information that is shared. There is certainly no meta data and no identifiable user data shared.

I hope that clarifies this for you and your client.

No problem at all, happy to help!

It seems like you’re getting some value from our Shield plugin – we’d be hugely grateful if you could drop us a review of the plugin and your experience in a review, if you’re open to it. These are very helpful for us.

Using a 3rd party provider is why this isn’t working as you’d expect. Each 3rd party plugin that Shield integrates with requires custom development to create and maintain the integration. These integrations are reserved for our paid members, as they’re typically deployed by business-related websites.

You can check whether Shield currently supports the provider you’re using under Shield > Config > Integrations > User Forms

If you’d like to get support for your 3rd party forms, you can upgrade via our website, or if you don’t see the integration you need, you can contact us when you’re a member to see if it’s possible and we’ll do our best to provide it – it more often than not depends on the 3rd party plugin and what integration options they’ve allowed for.

As these forums are specifically focused on Shield Security free edition, we can’t go into much more detail here about our pro products, but you can always reach out to our support team and other members on our Facebook group.

Update: A document outlining the DB tables and how you might manually delete logs is to be found here: https://help.getshieldsecurity.com/article/791-understanding-the-shield-database-tables

Always ensure you have any necessary backups before doing anything like this.

Hi,

It’s not currently possible to manually delete logs from within the plugin UI, the best way is to use the auto clean options. If you’re familiar with MySQL and comfortable working with the database, you can truncate the logs tables. If you’d like more details on that, please let us know and we’ll share it.

Thanks.

Hi,

Thanks for reaching out about this. Could you point me to your user registration form, please? Is it the default WP Registration form, or that from a 3rd party plugin?

Thanks!

Thanks for reporting these, we’ll take a look.

A number of my clients are starting to report this to us. Is there any chance you could rectify your autoload classmap as soon as you can? This change was introduced with the 2.2.2 update:
https://plugins.trac.www.ads-software.com/changeset/3054260/content-control/trunk/vendor/composer/autoload_classmap.php

The classmap didn’t contain the Pimple class before that change was committed.

I’ve responded to the other ticket to outline the source of the issue:

https://www.ads-software.com/support/topic/errors-on-2-2-2/#post-17514258

Hi all,

We understand the issue of prefixing, but that’s not what exactly is causing the issue here.

Shield uses the Pimple container class, and since it’s not prefixed, it should find it within our vendor folder. But it’s looking into your vendor folder for it (probably happening if your autoloader is installed after ours). Since your Pimple class is prefixed, we wouldn’t expect that to happen as the namespace/class names are different.

But it is. So this suggests to me that your autoloader is still referencing the original, unprefixed class, and when the PHP autoloader goes in search for the file, it’s not finding it on disk.

I just looked up your autoloader.php and discovered that it IS in your autoloader:

https://plugins.svn.www.ads-software.com/content-control/trunk/vendor/composer/autoload_classmap.php

Line 210:

'Pimple\\Container' => $vendorDir . '/pimple/pimple/src/Pimple/Container.php',

This means your autoloader is invalid… it’s referencing classes that you don’t actually have present on the disk.

I hope that makes sense and you can remove those invalid autoloader references.

Happy to help further if there’s anything else we can do. We will eventually prefix our classes, but in this case, this isn’t what’s going wrong.

Thanks again for your help!
Paul.

Can you try deleting and reinstalling the plugin, perhaps all the files didn’t copy over during install…

I’d need to know the plugin and what changes were made.

Also, we primarily provide technical support to our premium members, so while you can provide these details of the changes, we make no committments to if/when any changes will be made.

This is our final response to this review post – please post any further technical questions to the wp.org forums and we’ll address questions there.

Great, glad you found the problem! ??

Thanks for sharing this, we’ll take a look for our next release.