Domi2015

Where can I send you the access ?

Yes, in the configuration, User’s blog is the primary-domain, only superadmin (me) has access there.

Siteadmin (client admin) and siteuser (client subscribers) are not member of user’s blog (primary domain), they are member of client-domain. The siteadmin was created when creating client-domain, and he adds siteuser. So they both not member of primary-domain (user’s blog).

When trunk version network activated, Postman settings cannot be seen by siteadmin on his own site (client-domain).

I cannot confirm that the siteadmin have manage_postman_smtp.

SiteAdmin not shown in Primary and ClientDomain admin page, only on Network admin page.
https://www.awesomescreenshot.com/image/732482/479bb5dc9dca16743e849f3918a886ec
SuperAdmin has manage_postman_smtp.
https://www.awesomescreenshot.com/image/732490/d4461fe1da13d1c95675f7dcdf13ee8e

In PrimaryDomain, there is no SiteAdmin:
https://www.awesomescreenshot.com/image/732488/289dc4a8d1cebf2144d61de01ee97b2b

In ClientDomain, SiteAdmin had no User-Role-Editor menu. User-Role-Editor menu only shown on Network admin page (at Settings), and PrimaryDomain admin page (at Users).

If you need, I could PM login access to the test host.

Already get the test host running. The trunk works fine.

The problem with 1.7.1 can be regenerate:
– I install a plain Bitnami WP multisite (4.3.1), with 1 primary domain and 1 client domain. WP installation’s standard 10 plugins installed not activated. Only MU Domain Mapping plugin activated
– I set siteadmin could access plugin menu.
– When superadmin install 1.7.1 from plugins menu and network activated it, the siteadmin menu on the client domain went blank.
– Without network activated each siteadmin could install the plugin well.

I installed the new trunk, and it behave well:
– When network activated, no trouble on siteadmin menu. Patch is working.
– Only superadmin on primary domain could setup Postman. The siteadmin dont get access to Postman setting menu. This is the different behaviour from pre-1.7 version.
(you need to notify previously network activated site about this).
– Without network activation, siteadmin could activate Postman on their domain, as usual.

The test host is still up, so tell me if you need any more test.

In multisite, there is Super Admin / Network Admin (me) and Site Admin (my client’s admins). It was set in All User on Network Admin menu. No customization on my host, and no security plugin installed.

Site Admin is not set as Network Admin too keep them from network wide settings, but they held administrator role for their own site/s. They could install local plugin in their site. I think this is the standard of WP multisite.

I will try the trunk on a trial host later. Great work.

Thank you.

I’m on 1.7.1, confirmed. There’s no problem with previous version.

The Apache error log is something like this:

[Fri Nov 06 01:08:01.696859 2015] [proxy_fcgi:error] [pid 29654:tid 139694482355968] [client x.x.x.x:y] AH01071: Got error ‘PHP message: ERROR PostmanWpMailBinder: wp_mail is already bound, Postman can not use it\n’, referer: https://primarydomain/wp-admin/network/plugins.php?plugin_status=all&paged=1&s

Triggered by Super Admin, the admin content can be viewed without any problem.

[Fri Nov 06 01:08:12.269679 2015] [proxy_fcgi:error] [pid 29841:tid 139694490748672] [client x.x.x.x:y] AH01071: Got error ‘PHP message: PHP Fatal error: Call to a member function printMessage() on a non-object in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/postman-smtp/Postman/Postman.php on line 312\n’, referer: https://sitedomain/wp-admin/my-sites.php

Triggered by Site Admin / users other than Super Admin, resulting in blank admin content with sidebar and toolbar intact. Happened for all sites / domains.

I cannot repeat the error, since I currently don’t have trial host. Its a Bitnami standard build Multisite host, with some 30 plugin, which I disabled one by one, and the problem cease after disabling Postman, and happen if only Postman network activated.

Hope it helps.