Hello, thanks for amazing plugin. It is work so mach good, very good. But, after change url secret i am can’t change anything in this settings page. Help please.
]]>Anyone who gets something like:
Plugin could not be activated because it triggered a fatal error.
Fatal error: Call to undefined function get_called_class() in XXXXXX/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 18
PHP function get_called_class() introduced in PHP version 5.3.0 and above. So this means in your server running older PHP version. Solution is in cPanel or other type hosting panel (depends on your hosting) in “PHP Configuration” if you can increase php version to minimum 5.3.0 or greater or contact hosting to correct that.
I had this situation and I would like to share to all others who face with this issue.
]]>My server error log is filled with hundreds of errors from Wsecure-Lite. I’m attempting to do some trouble shooting of other plugins, and seeing this has me concerned that WSecure might be dysfunctional and should be uninstalled?
Anyone have any suggestions? Is this plugin out of date or flawed? Thanks for any suggestions. MTN
Examples below:
[18-May-2015 17:23:00] PHP Warning: session_start() [function.session-start]: Cannot send session cookie – headers already sent by (output started at /home/website /public_html/wp-content/plugins/wsecure/wsecure-authentication.php:15) in /home/website/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 15
[18-May-2015 17:23:00] PHP Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/website/public_html/wp-content/plugins/wsecure/wsecure-authentication.php:15) in /home/website/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 15
Hi,
I am getting the same error in two websites after filling out basic configuration in wSecure Lite and saving it. This is the message I get:
Warning: Cannot modify header information – headers already sent by (output started at …/mydomain.com/wp-admin/includes/template.php:1877) in …/mydomain.com/wp-includes/pluggable.php on line 1178
Fatal error: Cannot redeclare class WSecureConfig in …/mydomain.com/wp-content/plugins/wsecure/params.php on line 2
As a result the plugin still works on the computer I was using when activating and configuring the plugin, but it is messed up on my laptop where I get the site to enter the admin key, it then takes me to my WP login page, but when I want to login there I get the wSecure Admin key page again, and therefore can’t login at all.
Permalinks are set and the params.php is writable and all the settings are the same as in one of my other websites where everything works perfectly.
There are no extra spaces in the php code of the problematic file (at least not around 1877 line) that can sometimes cause this problem.
Deactivacting the plugin also didn’t help.
Any idea what else could be causing this? Thanks!
]]>With the update. Have to rename the plugin folder to access again.
]]>After updating the plugin to 2.3, I can not log in to my website. Previously, at a secret login page, I saw 2 columns – username and password. Now on the same page is displayed title “Admin Key” and “Enter security key.” after I enter the password, it is redirected to the main page and nothing else.
The same page “Admin Key” I see, even if I enter https://www.mysite/wp-admin/ or any other address.
Not immediately, but soon after moving from WP 3.9.2 to 4.0 the site started asking for my admin key when trying to log-in via wp-admin. I disable wsecure by renaming the plug-in folder and the problem was solved.
On another site, again, not immediate after moving from 3.9.2 to 4.0 but soon thereafter, all plug-ins failed to update. All plugin file permissions had been changed to 755. Disabled wsecure, changed file permissions, problem solved.
Seems like wsecure is not 4.0 compatible, or is that a coincidence?
]]>I am using v2.1 of wSecure on a single-site install of WP 3.8.1. The plugin activates ok, but will not enable. If I change the Enable setting from ‘No’ to ‘Yes’ and enter a simple text-only Key and click Save; the page refreshes with the message “Settings Updated” but the Enable setting has reverted back to ‘No’.
]]>I’ve used Wsecure on a number of sites without any problems at all. In fact it’s one of the first things I install on a new site. But I’ve run into the “can’t log out” problem on a site I’ve recently inherited. The site runs WooCommerce and I suspect the problem is that Wsecure and WooCommerce are bumping heads in the logout arena: as soon as I disable the Wsecure plugin the “can’t log out” problem goes away.
To try to fix or at least work around the problem I’ve tried various permalink structures as suggested by several people here, but none of what I’ve tried has worked. So I’m hoping that someone who has been successful in solving the logout problem will kindly post their permalink solutions.
Or is there another way, other than removing Wsecure and using another backend obscuration technique (that would be my very last choice: I really like the token key idea and use it on Joomla sites all the time)
]]>Worked fine until updated to 3.5.2
]]>I’ve installed your plugin on a site that has a couple of password protected pages.
Unfortunately, your plugin, when activated, causes the passwords to fail and redirects the user to custom path set up in the plug-in’s options.
Is there a workaround for this?
Thanks in advance,
Michael
]]>I installed it on two sites today (just discovered this plugin today as well), and on the first site, it works as expected.
On the second site, it fails as noted above.
I’ve changed the permalink structure, but that offered no solution to the issue.
]]>I found this on error_log
Am I under attack, bug, or server problem?
[22-Jan-2013 06:57:41] PHP Warning: session_start() [<a href='function.session-start'>function.session-start</a>]: The session id is too long or contains illegal characters, valid characters are a-z, A-Z, 0-9 and '-,' in /home/wpname/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 15
[22-Jan-2013 06:57:41] PHP Warning: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cookie - headers already sent by (output started at /home/wpname/public_html/wp-content/plugins/wsecure/wsecure-authentication.php:15) in /home/wpname/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 15
[22-Jan-2013 06:57:41] PHP Warning: session_start() [<a href='function.session-start'>function.session-start</a>]: Cannot send session cache limiter - headers already sent (output started at /home/wpname/public_html/wp-content/plugins/wsecure/wsecure-authentication.php:15) in /home/wpname/public_html/wp-content/plugins/wsecure/wsecure-authentication.php on line 15
Thanks
]]>Hi guys and author of the plugin. Just to keep this plugin perfect as is. There is small issue or bug in case if you have shopping plugin or any other plugin that uses PHP sessions.
I.e. when you have issue in shopping plugin when uses session to memorize shopping chart items list and when you reload, change page; shopping chart items list disappears.
This plugin erase session completely.
Here how to fix it. To can keep both plugins to work in same time.
Edit includes.php wSecure plugin file via WP editor or with some text editor.
Find and replace code lines (you have in three places on line 44, 57 and 69):
session_destroy();session_unset();
with
unset($_SESSION['jSecureAuthentication']);
or/and
session_destroy();
with
unset($_SESSION['jSecureAuthentication']);
This is my solution that works okay for me. If anyone have better solution let me know.
]]>thank you
]]>Anytime I’m trying to log out I’m redirected to my custom 404 page, but still I’m logged in. Is there a fix for this issue?
thanks + regards
]]>I’m getting the following error when logging out from the Dashboard/admin/backend. I’m using the Advanced version 1.1 but line 68 of 1.1 is the same as line 65 of the free 1.0 version.
Warning: session_destroy() [function.session-destroy]: Trying to destroy uninitialized session in /path/to/wp-content/plugins/wsecure/includes.php on line 68
Warning: Cannot modify header information – headers already sent by (output started at /path/to/wp-content/plugins/wsecure/includes.php:68) in /path/to/wp-includes/pluggable.php on line 866
I’ve checked to make sure there are no blank spaces or lines before <?php or after ?>
Not sure what else to check except this is line 68 (or line 65 of the free version:
session_destroy();
I’ve reported it to the authors, but I’m curious if anyone else has any ideas.
Thanks.
]]>This is just a tip, in case you have problems using this plugin. Make sure you’re using some permalink structure other than the default. Otherwise you will have problems, like not being able to log out.
Otherwise nice plugin.
]]>