specific user error on custom component
We created a custom component for the users settings which was working fine for a long time. But for some weeks now some users are complaining about that the widgets aren't loading on this specific p...
Forum Discussion
Did you check if Toolbox on production gives more details around the error?
Also, not sure why you're requesting json from the rest api and then calling an "xmltohash" function, but looks like what you're generating is not a valid FreeMarker hash and therefore ?eval fails.
If you have an admin account, you can perform the rest call and compare the output for an affected user with the one that is working...
Yes, as written above we already compared the rest call with other users but we couldn't see any difference.
I don't know why it has been implemented that way, but it was working as it is for a long time. We just don't understand why we are getting this error for a minor group of users now.
- Could it be that part of profile info of the affected users is interpreted as relevant characters for the conversion to XML? E.g. it could be that their signature contains XML or other code.
