Christian Gatti

Hi!
This is definitely not a problem related to Separate Login Plugin and furthermore, as I wrote here this plugin is no longer maintained.

Ragards,
Christian

Unfortunately this feature is not easily implementable, because it wasn’t planned during development. You should hardcode plugin scripts and you’ll loose those changes in case of future updates.

Regards,
Christian

• This reply was modified 7 years, 1 month ago by Christian Gatti.

Thanks!

As you said here, “security check error” is not attributable to Separate Login Plugin. So you should investigate your custom code.

Bye,
Christian

• This reply was modified 7 years, 2 months ago by Christian Gatti.

Hello again,
since your problem is not related to my plugin, this is not the right place to discuss it. Moreover, since you’re referring to a generical procedure (triggering), I guess you can find a pletora of people willing and able to help you on Stackoverflow or places like that.

Thank you,
Christian

• This reply was modified 7 years, 2 months ago by Christian Gatti.

Hi bonesteelkat!
“Security check” error is related to a failure during WordPress nonce verification and I guess is due to a small bug that I have fixed on the new release that you’ll find available in few minutes.

Please, let me know if the new release solves your problem.

Thanks,
Christian

• This reply was modified 7 years, 2 months ago by Christian Gatti.

I’m afraid I can not help you with those problem since I guess they are not strictly caused by Separate Login Plugin.

You’re definitely in the right direction!

• DB tables “seplog_sessions”, “seplog_translate” and “seplog_users” have to be placed into your external DB (you can use phpMyAdmin export/import functions)
• add into separate-login.php your new wpdb instance: $mydb = new wpdb(‘username’,’password’,’database’,’host’);
• search and replace $wpdb with $mydb into all plugin files

You’ve done!

“seplog_sessions” table is used to manage login sessions, so you must create it in your db too.

Regards,
Christian

Release 1.2.7.1 includes a new shortcode (“[seplog_show_to_everyone]”) useful to display content to everyone, regardless of user is logged or not.

Delete button added in 1.2.7.1 release, available now for download.
In order to delete a user, you first need to suspend him. After a user is suspended, a new “delete user” button will be shown.

Christian

Thanks to both of you.
So we should expect an official Sensei update soon, including all the changes that you reported, right?

Marked as solved, since no further reply was sent.

Yes it is 1.9.12!

The browser should not affect the correct execution of this plugin and, according to the tests I made right after having read your request, I can confirm that the browser is irrelevant. Maybe you are dealing with a plugin or a theme conflict.

Please, try to deactivate all the other installed plugins and let me know. If you get the same behaviour, please try another theme (only for a couple of minutes, just to see what it happens).

Is your site hosted on a Linux or a Windows server?

Regards,
Christian

Hi wardari,
the short answer is: you can’t. I mean that, as things stand now and without modifying the plugin code, you can delete users only by deleting the relative row into DB (seplog_users table); also, you could suspend users, so that they will not able to login until you’ll decide.

Christian