sspengler

Hi Faria,

thank you for getting back to me on that topic. I’ll test the update on our server as soon as possible and let you know if it works on our side.

Kind regards
Sarah

Hi Faria,
thanks for the fast reply. Looking forward to it ??

Hi Champ,

yes we are using a third-party plugin to create, display and manage custom database entries for our users. And I know that this has basically nothing to do with UM.

The problem is that a certain user role was able to edit these custom fields. But ever since UM v2.1.8 users of that role can still see the input fields on user-edit.php, but changes are not being saved. Only the admin role is able to successfully save these fields now.

So my question would be: did UM change something about user roles in v2.1.8 and following? It can’t be a coincidence that the user role is working correctly when I roll back to v2.1.7., I think.

Kind regards

Thank you, version 1.5.3 fixed it <3

Thanks for the fast reply!
Here are the screenshots you asked for. Hope they help.

• https://www.uni-electronic.de/screenshots/URE-Usermanager-uptodate-1.png
• https://www.uni-electronic.de/screenshots/URE-Usermanager-uptodate-2.png

Kind regards

Hello again,

I have gathered more information about the error:

The messages differ:
Chrome: Unexpected token < in JSON at position 0
Firefox: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Edge: JSON.parse Error: Invalid character at position:1

The error might have something to do with the plugin “Login Logout Register Menu”, that we also use. I deactivated all plugins except a few needed ones and the submit button on the UR register form stopped working. Then I activated the plugins again, one by one and checked the submit button. When the plugin “Login Logout Register Menu” became active again, the button worked like normal, and the error message appeared again, like before. Unfortunately this plugin seems to be abandoned. Deleting it doesn’t help either…

If you like, you can test it yourself: go to https://test.uni-electronic.de/kundenbereich-registrierung
To reproduce the error, use Test-04 in the input labeled with “Ihre Kundennummer”, which would be the user’s WordPress login name. The other inputs (company, mail, password) can be anything you like.

Another idea was to rollback the UR version, but I went back to v1.8.1 and the error also exists there.

Hope this helps!
Kind regards
Sarah

Hello Support Team,

we have a similar problem and get the same error message. For us it only pops up when we try to register a new user via a UR form and the user trying to register uses a login name that already exists. When they use an email address that already exists, a standard message like “email already exists” appears after submitting the form.
But an already existing user name results in a red “Unexpected token < in JSON at position 0” error message.

I copied our WordPress installation to a test subdomain and deactivated all unneeded plugins, but that didn’t help much in finding the error because then the submit button was dead…

Then I tried to create a workaround in the functions.php by “translating” the error text to a human readable message like “your user name already exists”. But that didn’t work either :-/

I also found out, that I already translated the UR error messages to our native language by using loco translate. And the translation is still active, but nonetheless, the error messages comes out as Unexpected token < in JSON at position 0.

This happens in UR Version 1.8.3 and 1.8.4- But I’m pretty sure it used to work before.

Any ideas? I’d be glad about any kind of response.