I set up the authenticator on my page, which does its job nicely and I am grateful for that. However, I want a website for marketing purposes, which I want to be public and accessible to everyone. I would like to ask what setting I can use to achieve this. Thank you in advance for your answers!
]]>Good evening, I have installed the authenticator plugin and would like to understand if it is possible to automatically redirect users directly to the frontend and not to the dashboard, in fact with the subscriber role the dashboard must not be accessible.
is this possible?
Thanks
]]>seems like i cannot get this to work with the wordpress mobile app.
first it seems to find the wordpress instance when i enter my url, but when i enter my username and password it says
Es konnte keine WordPress-Website unter dieser URL gefunden werden.
when i deactivate the plugin the wordpress app can login without a problem.
i think last time I tried it was no problem to login, any tipps how i can get this wo work with the WP App?
thanks
]]>Hi Frank!
Is there a possibility to get this plugin working including an authenticated request to the REST-API with a token like for the feeds?
Thanks,
Marc
I was wondering whether your plugin was still compatible with the most recent WP version 5.7.2?
Thank you very much for any information on this issue.
]]>www.remarpro.com and WordFence are reporting it as abandoned, though it still works fine and is listed on your web site as a current project. I’d hate to have to look for a replacement!
Can I suggest you do a minor update (indicate that it’s “tested up to x.x” or something) just so that we know it’s still alive?
]]>We use the plugin event espresso and have a problem in combination with your plugin. I got the following message from the support from event espresso:
I checked the Authenticator plugin and as far as I can tell, it blocks all REST API requests. Even requests that include Basic Authorization. You could contact the developer of the Authenticator plugin and ask them if they can change the plugin so it can allow REST API requests that include HTTP Authentication (Basic) with Username/Password of the WordPress account.
We also use shibboleth as IDP.
How do we get everything work together?
]]>Hi,
Is it possibile to redirect to another login page and not wp-login.php please?
How can I do it?
Hello,
On my website, I’d like to have pages for only logged in users and pages for every body (logged in and not logged in). How must I do ?
I have already install Authenticator and I think I have to use these words : “authenticator_exclude_pagenows” but I don’t know how. Can somebody tell me ?
Thanks,
Valérie
Thanks for this plugin.
Is it possible to enable user specific token. So i can use different token for different users.
Request your help on this.
]]>Hi there!
I just wanted to tell you that the new version of the plugin prevented me from accessing my dashboard (internal server error). After re-installing my previous version from a backup everything worked fine again.
Best wishes!
]]>I have established that password is not my issue, which means the only solution is that Authenticator is what’s not allowing me entry to my site. Any ideas how to rectify this? (Preferably without accessing FTP, as I don’t have a program that will open and allow me access to FTP.)
My website: https://www.breecrowder.com
]]>I’m having problem with my wordpress account, after login it request for authentication code which I lost on my system and also the application was lost on my mobile. I checked from my host server file manager if I can find the plugin so as to delete it but I can’t find the authenticator plugin there. Please how else can I resolve this? I can’t loose my website like that.
]]>Hi,
first off, I’m German, so I’d be happy to ask this in German, but as it’s an English forum, I thought it’s better to do it in English.
This is a functionality question – I’ve been researching a way to protect certain uploads from being shown to people who are not logged in, even if they have a full URL. I thought this solution was the way to go –
https://wordpress.stackexchange.com/questions/37144/how-to-protect-uploads-if-user-is-not-logged-in
but when I realized that your answer to the thread has been incorporated into authenticator – or at least it seems that way – I tried the plugin to that effect, and it did not do it (on a clean install of WP4 multisite).
In the end, I’m hoping to go beyond Authenticator and check for the post_status as it is made possible by the code you put in the thread above and improved for Authenticator, but so far it seems that it does not work – at least not for me in this installation of multisite.
Does this specific part generally work? I’ve also asked a question here – https://wordpress.stackexchange.com/questions/165293/how-to-protect-specific-uploaded-files-from-being-accessed-by-non-logged-in-user
Thanks & Danke =)
]]>as I can do to enable user registration with the installed plugin?
the only thing you can do it without being logged in to register?
thank you
is it possible to create an authentication token for (individual) page or site access?
]]>Will this plugin allow for only 1 user to login with the same user name?
]]>Since I need to use JSON to retrieve the recent posts from the website that I should add the user login in the URL: https://m1.server.com/?json= get_recent_posts?login=admin&password=adminpwd . May I know any solution for it?
]]>On Logout:
******************************************
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /wp-includes/functions.php on line 3049
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 415
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 427
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 695
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 696
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 697
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 698
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 699
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 700
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 703
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 704
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 705
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 706
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 709
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 710
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 711
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 712
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 896
On load of wp-login.php:
******************************************
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /wp-includes/functions.php on line 3049
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 415
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 427
After login click on wp-login.php:
******************************************
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /wp-includes/functions.php on line 3049
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 415
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-login.php on line 427
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 678
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 679
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 680
Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:3049) in /wp-includes/pluggable.php on line 896
]]>
Hello,
How do I change only the logo of wordpress.
Caesar.
Hi Frank,
thanks for the great plugin, that’s exactly what i was looking for my wedding page. Is it a big deal to change the login screen design, i.e. a different title and logo? I am excited to hear from you.
Cheers Nick
]]>Hello and thank you for this plugin.
I have a question about the page that appears after a user logs in. Sometimes, the WordPress dashboard/profile appears. Sometimes, the index page of the blog appears. Can we control this? I would like the index page of the blog to appear instead of the user’s profile page.
]]>I have a multisite with 2 blogs. One is public one should be protected.
Everything works except one part – when i enter the URL of the Public Blog the redirect goes to https://www.domain.com/wp-signup.php?new=domain.com
It is only installed on the protected blog – no caching – only basic multisite…
Any ideas?
Thanks
Patrick
I was using the “Authenticator” plugin to password protect my blog while it was under development. I have disabled the plugin but some users are still redirected to the wp-admin login page. I have also tried removing the plugin completely but still have the same problem.
The problem only affects a small percentage of users, as far as I can tell. Any ideas for how to fix this?
]]>