Multisite-old method not working

Could not get the new version to work at all. I put the blogs field 5th after username, email, password, and role. No records were added or changed, regardless of whether I ran the plugin on one of my class websites, on the main member website that has all 3XX members, or on the first website in the multisite which is public and has no members.

When I tried the “old” method of adding members to the specific website (described in my earlier email), I did get notice that my new people got an email (BUT DIFFERENT THAN THE EMAIL MESSAGE I WROTE AND SAVED), but they still didn’t get listed on that class’ member list (i.e., users).

Could not get the new version to work at all. I put the field called blog 5th after username, email, password, and role. No records were added or changed, regardless of whether I ran the plugin on one of my class websites, on the main member website that has all 300+ members, or on the first website in the multisite, the one that is public and has no members.

On one effort (and I don’t know if it was the new or the old method), I did get a notice that my new people got an email (“New user registration on your site…”) but it was a different email than I had written and placed in the Mail Options tab. In another test of the new method, people got a message that they needed to set a password. But they all had a password for the multisite.

Something’s really wrong here, and it’s disappointing because it has worked so well in the past.

One more clarification. Earlier today I added 30 people successfully to the main member website. They were all NEW adds. The people I was trying to add to the individual class websites were all existing users on the main website. They just weren’t existing users on the site I was adding them to. I never had a problem with that before, but perhaps that is what is not working for multisites.

@machank,

Sorry we have not change anything about it in last version, so I don’t know where can be the problem.

Could you tell me in which version it worked? With this info we can compare between it and check where can be the problem.

Thanks for replying. I can tell you when I used it last successfully which was last January. Generally the version I use is the most recent at that time.

Is the old method still supposed to work for multisite? That is, adding members to the subdirectory/site (class) who are already in the member list for the multisite in another subdirectory/site (“all members” site). What happens is that it looks like it works–I get a list of “new users” but then the user list for that class doesn’t change. [I did a couple of screenshots to show you but this comment window doesn’t allow graphics.]

And how does the new method for multisite work? I entered the CSV file listing a test file of 3 users already in the multisite and used a column called “Blog” putting in the site IDs (e.g., 2, 25) and nothing happened at all.

This plugin never has been able to add users to another blogs. Only to the current one:

// Multisite add user to current blog
					if( is_multisite() && ( $created || $update_roles_existing_users != 'no' ) ){
						if( !empty( $role ) ){
							if( is_array( $role ) ){
								foreach ($role as $single_role) {
									add_user_to_blog( get_current_blog_id(), $user_id, $single_role );
								}	
							}
							else{
								add_user_to_blog( get_current_blog_id(), $user_id, $role );
							}
						}
					}

I am not a MU user so I never found it useful, but we can improve it.

What about a column called blog (or something like it) where you can place a list of blog_id where you can assign the user.

Tell me if you think it could be useful or if you would prefer to do it in a different way.

I thought that’s what you meant with the following from your documentation page:

“Multisite is activated Plugin can assing users to blogs after importing them roles. This is how it works:

” You have to create a column called ‘blogs’: if cell is empty, it won’t assign users to any blog; if cell has a value, it will be used. You have to fill it with blog_id
Multiple blogs can be assigned creating a list of blog ids using commas to separate values.

—–

But while that would be nice, the way I use your plug-in is to add people to individual class sites (i.e., subdirectories) one class at a time. That’s the way I had been using Import/Export/etc. for the past 3 years on this same multisite.

Finally, let me put in a plug for the broad applicability of multisite. There are many organizations with components that involve a subset of organization members. For organizational websites, it is important to allow access (and notifications using notification plug-ins) just to the members of that component (class, in our case). WordPress provides a great structure for this, but we need to be able to assign members to each component independently. Note that in our case, people can have more than one class, so each component needs to be able to be populated independently. It’s not just dividing the large group into non-overlapping pieces.

So my request is to somehow return the plug-in to the way in worked before on multisite. That is, if I had the person as a member in another site in the same multisite, I would add them to the new site as an existing member…(I’m not sure what other use one would have for the “existing member” add) It worked perfectly!

@machank,

We will fix it in a future but we are really busy now.

Sorry for any inconvenience but we will do.

I have been able to check it.

It is working. If you create a column called blogs and you fill it with a list of site ids and it will work.

I don’t use it and this is because I was not sure about it but it has not be changed.

Hi Javier,

I’d like to report on how I finally resolved the problem of adding “existing” users to another site within a multisite setup. To refresh your memory, when I had members of the multisite who were not yet members of one of the specific sites, I would add them to that site by “update existing users” and it looked like they were being added, but they weren’t in fact added.

What I discovered just now is that if I changed the box “update roles” from “no” to “yes” then they WERE ADDED as desired. It wasn’t obvious that that would be needed but in fact that was the trick that made it work.

Ok, it seems to be a bug.

If you do not want to update roles, you should be able to add roles to the sites with a default role (or the same role they have in other site).

I will check it and fix it.

I have just fixed it, update to the last version and test please.

If it fails, ask me again.

Thanks. I just happened to notice that you had updated the plugin to address my problem. I will test it in the next week and let you know if there are any problems.

@machank thanks!