You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, since the forum is "down" (spammed beyond recognition), I'll "report" the issue here.
I have a problem with the length of usernames in: Management -> SystemUsers -> New User
In the Create new user view there is a validation of the username length (20char) which is rather low. We are currently using email addresses as usernames, and an email can quite easily become 20+ char.
Is there any way to increase the limit in the view? (the db tables ranges usernames from 100char to 255 (to text)), so it is not looking at the DB field lenght.
Hi, the validation is located in SystemUserVO.java as all entity validation currently is. It's very easy for us to change and if you enter this in the Infoglue Jira (http://community.infoglue.org/jira) I will be happy to fix it instantly. A small problem though is that for indexing, gui and performance reasons we must have a limit to the number of allowed characters. What would you say is a large enough limit? Put that as well in JIRA.
Hi, since the forum is "down" (spammed beyond recognition), I'll "report" the issue here.
I have a problem with the length of usernames in: Management -> SystemUsers -> New User
In the Create new user view there is a validation of the username length (20char) which is rather low. We are currently using email addresses as usernames, and an email can quite easily become 20+ char.
Is there any way to increase the limit in the view? (the db tables ranges usernames from 100char to 255 (to text)), so it is not looking at the DB field lenght.
The create new user view is defined in https://github.com/bogeblad/infoglue/blob/master/conf/cms/actions.xml, but I have not been able to locate any length validation anywhere.
In short can the input validation be increased? (preferably through the interface)
The text was updated successfully, but these errors were encountered: