One Dollar Plugin
Forum Replies Created
-
Sure, these could be possible… we can investigate them. As to them being “easy”, we don’t know yet. In all likelihood we would release this under our ShieldPRO plugin.
Thanks for the suggestions.
Forum: Plugins
In reply to: [Flexible SSL for CloudFlare] broke 2 of my siteDid you follow the guide exactly?
https://icwp.io/6zForum: Plugins
In reply to: [Flexible SSL for CloudFlare] Unable to install on 5.4 WordPress versionYes. This error should now be gone.
Forum: Plugins
In reply to: [Flexible SSL for CloudFlare] Unable to install on 5.4 WordPress versionWhat do you mean exactly that you cannot uninstall it?
I’ll assume you’re referring to user login/registration protection.
If that plugin uses completely custom login/registration forms and these don’t call start WordPress hooks/filters/api during processing, then no, Shield does not support it.
However, ShieldPRO supports many 3rd party plugins like WP-Recall and if it’s not supported just now, we can add support for it. If this is something you want to discuss further, please reach out to us outside of these forums as we can only offer support for ShieldFREE on these forums.
Thanks
Hi Brandon,
Thanks for your message and suggestion.
The issue with this sort of labelling is that it can be easily misunderstood and it’s not as trivial to identify a bot as it may first appear – this is the major challenge we try to overcome.
Malicious bots can “pretend” to be human visitors and disguise themselves in a very trivial manner. Labelling this as “not a bot” can be easily, and for many bots, altogether wrong.
Disguised bots can be identified as-such when they exhibit bot-“like” behaviours, but this often requires a number of signals to make this determination (which Shield does automatically also, in order to block disingenuous bots).
To learn a bit more about bot signals etc., you may wish to read up on it here:
https://onedollarplugin.com/blog/bot-signals/Also, on top of this, Shield automatically verifies and filters legitimate search engine bot traffic, so you wont even see these bots in the traffic log in the first place.
So for the traffic watcher, we lean towards simply cataloging the traffic as it comes through, and wherever possible not placing labels on it which are very possibly incorrect.
I hpoe that all makes sense, and I appreciate your suggestion, Brandon.
There was nothing condescending or ridiculing in my response. You may feel otherwise, but that doesn’t make it so.
I responded to your post for the purposes of clarifying things for potential readers of your review and laid out clearly the misunderstanding you have about how the Security Admin key works.
Our helpdesk records indicate you were given a full and complete response to your ticket sent to our helpdesk. You didn’t respond to it to say you needed further help or clarification, except to respond a few days later with an email of 5 words: “This has not been resolved”. That was the last we heard from you, 20 days ago.
As our response stated, the admininstrator creates the key. You may dispute that, but unfortunately the only way to prove this to you is for you to read the source code. It’s all in there.
I’m sorry you haven’t had a great experience with the plugin, but your attitude towards has been none-too-friendly from the outset, but we have responded politely and with the information you needed when you asked.
As a small business owner yourself, you can try to imagine how you’d respond if someone reached out to you for help, with the tone and the manner you have done with us. Yet we helped you anyway.
Best of luck out there.
It seems you’re using a plugin/theme that is customizing your comment form in some way, away from the standard WordPress comment forms. Shield can’t integrate with customized comment forms without custom coding. We have a Pro-only feature for handling some of these scenarios, but it’s pro usually because it requires help from our support team to handle.
What’s your URL?Hi,
We reply, when we can to most questions put to us. We do what we can.We’ll try to improve RTL support for the next couple of releases.
Hi Jadene,
We got your support ticket request also, here is what we said in that ticket:
Sorry for the trouble you’ve been having.
Shield Security doesn’t “come with” a security admin key… it must be added by an administrator in every case.
So it’s likely that you, or another admin, set it a while ago and have since forgotten it. The only way to unlock it thereafter is to reset the plugin entirely, or use the forceoff feature to recover access to the plugin and remove/reset the key.
Alternatively you can just delete the plugin and any issues with the plugin will be immediately removed. If you’re not familiar with FTP, then you could use your webhost’s file management tool to do the same job. Look for wp-content/plugins/wp-simple-firewall/ and just delete that directory.
If you’re unfamiliar with that, you could ask your host to perform the task for you and that’ll then clear up any further hassle with the plugin altogether.
Thanks,
Hopefully 8.3 will resolve this for you.
But the issue around cookies can be resolved by notifying visitors of the use of cookies and explaining what they are. They can accept that or reject it.
I think the GDPR legislation is designed to ensure that users/visitors are generally better informed about what’s happening, and give them more options, not prevent the use of cookies.
Could you share your url?
Hi, sorry to hear about your trouble.
If you have removed Shield Security and you still have the problem, then: the problem was never caused by Shield Security.
When you’re trying to access the admin page, delete the content of the URL and type your website + /wp-admin/
There are only very specific scenarios where that cookie is set.
It’s never set for normal visitors, unless they visit non-normal pages, such as the login page.Can you test again by ensuring your cookies are definitely cleared and loading only, for example, the home page.
Also, please ensure you’re on the latest version of Shield.
Hi Robert, are you seeing a cookie being set for non-logged-in users?