Add site fail (custom user role)

[Fixed]

Hi guys,

We recently realized that if we try adding a site via a user with role different than “administrator”, it fails with this error:

And the front-end gets stuck to:

It was tested on multiple devices/browsers and in incognito mode.

The load-scripts.php file is from WP core so I thought it may be due to some recent core release but we tried downgrading to 6.8 and it’s still the same.
This leads me to believe that it may be due to a more recent MainWP ver change. We’re currently on 5.4.0.10 and I believe you’re already quite familiar with our setup.

The user roles do have perms for Add Site (via Team Control), and this was working before with no recent changes on our end.

Could you please test on your end by adding a site via a user with a custom role (different then “administrator”) and advise if this is a potential bug?
If the user is “administrator” it works properly.

Thank you!
Fixed .net

[bojan (Bojan Katusic)]

Hey @Fixed

I couldn’t reproduce this on using Dashboard v5.4.0.11 and Team Control v5.0.2.

I used a Team Control role which had these Sites permissions:

The site was added without any issues.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?

Please refer to this Community thread by its URL in the ticket.

[Fixed]

Hi Bojan,

Could you please try again after un-checking the “Manage Clients” option?

We tested by going through the list and it sometimes adds it successfully after enable/re-enable the following:

“Manage Clients”
“Bulk Install and Active Extensions”

It is a bit random behaviour but it appears to be affected mostly by “Manage Clients”.

Thanks again,
Fixed .net

[bojan (Bojan Katusic)]

Thanks for that additional information.

I’ve managed to reproduce the issue when “Manage Clients” and
“Bulk Install and Active Extensions” permissions are not granted in Team Control.

The process stalls on Adding the site to your MainWP Dashboard. Please wait... with the same error in the browser console.

I’ve passed it along to our development team and it will be fixed in an upcoming release.