I am trying to: create a new user, from a non-administrator user (which has access to BE, but has no access to any translation related thing, nor related capabilities. but ATE js is loading and breaking because rest "retry" api returns 403 forbidden... which is correct since they don't have the capability).
Link to a page where the issue can be seen: /wp-admin/user-new.php when logged in as "Staff" user role.
I expected to see: I just want to create a new user, without js issues.
Instead, I got: I can't do it because of js issues.
I've also tried to: I read the ATE code and I see that if I assign the manage_translations capability to the Staff role users, it won't break. That's right, this works, but doesn't make any sense. I don't want them to be able to manage translations at all.
Can you please try to reproduce the issue in a dummy simple example?
I created a minimal installation of WordPress, WPML, and all necessary WPML add-ons.
You can access the WordPress dashboard using the link below:
- hidden link
Kindly follow the steps below:
- Set up WPML
- Try to replicate the issue with dummy minimal example
- Share with me step by step guide on how can I check the issue
This will help us to report faster the probable issue to our team./em>
1) Go to the user list: hidden link
2) Switch to the staff user (I installed user switching plugin)
3) Go to Users > Add new and check the javascript console.
Damn it, I touched something and the error disappeared, I'm unable to replicate it anymore (on your demo). Can you please create me another empty demo like before?
Also, can you please try to reproduce it without additional plugins, like the user switching plugin. That way we can confirm it happens when only WPML is used and not caused when in combination with any other.
Feel free to share credentials and test steps in your next private reply.
1) Right, it still possible to create the user; in my live site, I have another error which lead me to think this was the cause but it's not;
2) I created the STAFF role using User Role Editor (cloned from Subscriber and added all the 'users' caps + edit_posts)
Since the "staff" user has absolutely no permissions about translations, I think the ATE scripts should not run at all. Yes, I think this must be forwarded to your devs.
is scheduled for a permanent fix in one of the next releases.
The message does not create any blocking in the backend. The error message is logged in the console when the request is not completed which is the case when a user does not have permissions. However, this is not the best practice and we will adjust and check if the user has permission before sending the request.
I will update you when the version with the fix is released.
