squidgemonster

Cheers Darren – really appreciated ??

Curious to know if there was a result from this investigation…?

Ahhh – great stuff, thanks Darren, fingers crossed we get to the bottom of this eh? ??

Thanks for the response Paul – I’m afraid I’m uncomfortable with giving access to the particular site in question as it’s one of my biggest clients, and should any investigations inadvertently lead to any issues with the site I’ll be in a world of pain!

Do let me know if there are any discoveries you make should Darren wish to give you temporary access, or if you have any thoughts based on the information already supplied that would be very much appreciated.

Hi Paul – I’d have to agree with Darren, I’ve described the issue in as much detail as I can in the post, and given it’s not a problem unique to myself, wouldn’t this be of benefit to solve/address in the support forum?

I don’t think it’s server-based for me, have a bunch of other WP sites on the same server which run the backups fine… glad I’m not alone though! ?? I’ll look into the versions of my LAMP set-up if that’ll help…

How are you getting on agreda?

The change WP 3.1 has caused all manner of issues with the ‘subscriber access’ vs actual ‘subscriber’ for the network, group, family(?!) of sites. I have to say that the plug-in I referenced fixed all the issues though as you can assign default user subscription levels to each blog/site(?!) which in turn will make them appear in the site admin for each site you’d like ??

I do think you’re right in asking if there is reason in WordPress’s madness for creating the psudo role to make it more flexible for the way that people might use multi-site set-ups… but I can’t see one.

Anyway, hope you’re making progress.

Hi agreda – thenbrent has just done an update to his great plug-in to fix the non-registration on the main/blog ID 1 site:

https://www.ads-software.com/support/topic/plugin-multisite-user-management-update-for-31

I can’t speak for him, but I’m sure this will be pushed out as an update for the main plug-in shortly.

I’m a little confused why this pseudo subscriber role is created for network sites as it creates quite a few problems, especially as general plug-ins tend to refer to users by role, not by capabilities… I’ve had to add hack/add ‘can_edit’ statements to adjust content for these ‘ghost users’ who don’t appear to belong to any blog…

You are a legend – just tested the beta and works like a charm ??

I don’t know what WordPress are thinking with the pseudo subscriber access… it doesn’t make much sense really, especially as so many plug-ins reference the users role rather then capabilities, and the pseudo users only being visible by the network admin…

Anyway, I can’t thank you enough, hopefully this has been helpful for your development as well… the plug-in still serves a VERY useful purpose ??

Mmm – I’ve noticed that they’ve said this, but unfortunately it doesn’t appear to be the case, any interrogations by role don’t flag those users as subscribers for each site – and they’re not listed on the individual blog user lists as subscribers (which your plug-in does do) – I don’t know if this is a fault with my installation of 3.1, or something I’m missing in the set-up of 3.1, but I do think your plug-in is still of use going forward.

I think the key here is that they say ‘subscriber access’ but the user isn’t actually registered as a subscriber for the individual site, which is different. Any test accounts I set-up add the user to the network users list, but they still have to be manually added to each site within the network.

Any thoughts?

Hi thenbrent – did you find any issues with 3.1 in the end?

Thanks for the quick response thenbrent, really appreciated. It would be great to see this working as it was before, great work on a great plug-in.