Hello.
We will remove this undisguised notification. Can you give us a link to your site so that we can check why this is happening?
Hello, the same is happening to me. I’ve updated 3 WP websites today and I’m getting this alert on all of them now. Even when I click the X to close it, it comes right back.
here is one website: http://www.ameliaislandrealestateforsale.com/
Titan security: HTTPS is not activated on this site.
This is incorrect. How do we correct this?
You log in to the admin panel using the http protocol. You need to configure redirection from HTTP to HTTPS.
Is Titan replacing Akismet?
Is it possible to uninstall Titan?
Our anti-spam works better than in Akismet
Thank you. That may be so. But can Titan be uninstalled?
@webtemyk Our admin url is /admin-login and it is also HTTPS
Disregard uninstall question. Had it handled.
Note: Titan may be awesome. But it is simply over complicated for me. When I look at the Titan dashboard it is confusing. And, it is intimidating.
In saying that, I wonder how I would feel if all I saw was the basic dashboard with links to tutorials and why I should upgrade. An example that comes to mind is Yoast. As I worked through their free plugin and tutorials, I realized the benefits of upgrading.
I share all of this to suggest that the WP platform has in excess of 30% of the market. But of those 30%, do you know what percentage of them are users like me, small business owner, no IT department, a do-it-yourselfer? If I’m your target market, I believe I am not alone in my observation.
-
This reply was modified 6 years, 1 month ago by
jdoucet.
Our admin url is “/admin-login/” and it is also HTTPS
@webtemyk Any further clarification would be appreciated if this is an issue on our end and not yours. Our WP Admin is also HTTPS protected and your previous response makes no sense since HTTPS Redirection is being handled by the plugin Really Simple SSL, as it should be already doing exactly that.
This notification was removed in the last update.
We are already looking into why there was a problem with defining the HTTPS Protocol
@webtemyk Great. Thank you for the update