Jan ?tětina

Guys, it would have been better if you had started a new topic for this.

Anyway, you should see a form to create new message on Network admin –> Dashboard –> Organizational messages – at the bottom of the page.

You are very welcome!

Hello Heather,

I hope current version (3.1) fixes the $wpdb->prepare problem. The other issue might be related… please upgrade and try if it persists.

You can see what exactly have I changed since last version here:

https://plugins.trac.www.ads-software.com/changeset?reponame=&new=641188%40multisite-user-registration-manager%2Ftrunk&old=619921%40multisite-user-registration-manager%2Ftrunk

Zaantar

ReCaptcha is on the wishlist. For now you can enter an Akismet API key and have registration requests checked by Akismet as if they were comments.

I’m not sure I understand your second question. Registration on the network level can be set to be approved automatically, if this is what you’re interested in.

Currently MURM creates new users with role “subscriber”. In the future it will be probably customizable.

Unfortunately I have no experience with Multisite User Management.

Hello,
very soon there will be version 3.1 which should fix this issue (it was a stupid typo).

Please confirm it is fixed after you update MURM.

Hello,
if you look into my code, you’ll see a method of the Murm class:

function load_textdomain() {
	$plugin_dir = basename( dirname( __FILE__ ) );
	load_plugin_textdomain( self::txd, false, $plugin_dir.'/languages' );
}

Ergo the correct WordPress function is called. However, I suspect that the Codestyling Localization plugin might think that load_textdomain is called because it just searches the murm.php file for this string and finds it.

I’ll rename my method to something else and you’ll see if the warning disappears. Please confirm afterwards.

Hello,
do you still have this problem with current version of MURM?

Unfortunately, I am not familiar with Multisite User Manager, however MURM stores request separately from the rest of WordPress database, so I believe that any kind of conflict is very improbable.

Hello,
does your problem still persist with current version of MURM?
What exactly did you change in the database?

Version 3.0 was very buggy, my bad. Do your problems still persist in 3.0.3?

The plugin should be activated for whole network, not for a single blogs.

It should be fixed in version 3.0.3. Please confirm.

I’ve added your request to the wishlist – currently there is no free time to implement any new functionality, but it will not be ignored.

Yesterday.

Version 1.1 with some fixes was released just a while ago. However more updates are probable in the future. Just wait for the WordPress update notifications on your site. ??

Yes, this plugin uses eval() and currently is considered unsafe… but I’m working on fixing these security issues. Stay tuned for next versions ??