掲示板
LR62.CEGA6 UserScreenNameException with ø
7年前 に darren rose によって更新されました。
LR62.CEGA6 UserScreenNameException with ø
Regular Member 投稿: 215 参加年月日: 15/04/04 最新の投稿
Hi,
I see UserScreenNameExceptions for screen names with Nordic Characters
How do I allow nordic characters? e.g. ø
I see UserScreenNameExceptions for screen names with Nordic Characters
How do I allow nordic characters? e.g. ø
7年前 に Samuel Kong によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Liferay Legend 投稿: 1902 参加年月日: 08/03/10 最新の投稿
That character is not allowed. Screen names are limited to a-z, A-Z, 0-9, dash(-), period(.) and underline(_)
7年前 に darren rose によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Regular Member 投稿: 215 参加年月日: 15/04/04 最新の投稿
Ok thanks,
7年前 に Alberto Chaparro によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Liferay Master 投稿: 549 参加年月日: 11/04/25 最新の投稿
Hi Darren, Samuel,
Checking the code I think you can use the following property to allow more special characters in the ScreenName:
Please, test it and let us know.
Regards!
Checking the code I think you can use the following property to allow more special characters in the ScreenName:
users.screen.name.special.characters=-._
Please, test it and let us know.
Regards!
7年前 に darren rose によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Regular Member 投稿: 215 参加年月日: 15/04/04 最新の投稿Alberto Chaparro:
Hi Darren, Samuel,
Checking the code I think you can use the following property to allow more special characters in the ScreenName:users.screen.name.special.characters=-._
Please, test it and let us know.
Regards!
have tried this, without success
users.screen.name.special.characters=-._ÆæÅåÄäØø
7年前 に Alberto Chaparro によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Liferay Master 投稿: 549 参加年月日: 11/04/25 最新の投稿
Hi Darren,
My apologies, that propery is for Liferay 7, I didn't realize that you were using 6.2.
In that case you could use the LiberalScreenNameValidator (take into account that it checks only that screenName is not null):
Or implement your own validator.
Let us know what you think.
Best regards.
My apologies, that propery is for Liferay 7, I didn't realize that you were using 6.2.
In that case you could use the LiberalScreenNameValidator (take into account that it checks only that screenName is not null):
#
# Input a class name that implements
# com.liferay.portal.security.auth.ScreenNameValidator. This class will be
# called to validate user screen names.
#
users.screen.name.validator=com.liferay.portal.security.auth.DefaultScreenNameValidator
#users.screen.name.validator=com.liferay.portal.security.auth.LiberalScreenNameValidator
Or implement your own validator.
Let us know what you think.
Best regards.
7年前 に darren rose によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Regular Member 投稿: 215 参加年月日: 15/04/04 最新の投稿Alberto Chaparro:
Hi Darren,
My apologies, that propery is for Liferay 7, I didn't realize that you were using 6.2.
In that case you could use the LiberalScreenNameValidator (take into account that it checks only that screenName is not null):# # Input a class name that implements # com.liferay.portal.security.auth.ScreenNameValidator. This class will be # called to validate user screen names. # users.screen.name.validator=com.liferay.portal.security.auth.DefaultScreenNameValidator #users.screen.name.validator=com.liferay.portal.security.auth.LiberalScreenNameValidator
Or implement your own validator.
Let us know what you think.
Best regards.
I have set this also:
users.screen.name.validator=com.liferay.portal.security.auth.LiberalScreenNameValidator
But that does not resolve the issue.
7年前 に Andrew Jardine によって更新されました。
RE: LR62.CEGA6 UserScreenNameException with ø
Liferay Legend 投稿: 2416 参加年月日: 10/12/22 最新の投稿
The LiberalScreenNameValidator basically imposes no restrictions, but that doesn't mean you can use whatever you want. I tried using this some time ago to allow characters (latin based) that aren't allowed by default -- but a second issue (for me anyway) came as a result of the user sites. In my case I was trying to use characters that are not allowed in a URL. In my case, I never found a work around for it -- even when I disabled the user public/private sites.
Can you share the whole stack trace with us?
Can you share the whole stack trace with us?