Forums de discussion

LR62.CEGA6 UserScreenNameException with ø

thumbnail
darren rose, modifié il y a 7 années.

LR62.CEGA6 UserScreenNameException with ø

Regular Member Publications: 215 Date d'inscription: 04/04/15 Publications récentes
Hi,

I see UserScreenNameExceptions for screen names with Nordic Characters

How do I allow nordic characters? e.g. ø
thumbnail
Samuel Kong, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Liferay Legend Publications: 1902 Date d'inscription: 10/03/08 Publications récentes
That character is not allowed. Screen names are limited to a-z, A-Z, 0-9, dash(-), period(.) and underline(_)
thumbnail
darren rose, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Regular Member Publications: 215 Date d'inscription: 04/04/15 Publications récentes
Ok thanks,
thumbnail
Alberto Chaparro, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Liferay Master Publications: 549 Date d'inscription: 25/04/11 Publications récentes
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!
thumbnail
darren rose, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Regular Member Publications: 215 Date d'inscription: 04/04/15 Publications récentes
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=-._ÆæÅåÄäØø
thumbnail
Alberto Chaparro, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Liferay Master Publications: 549 Date d'inscription: 25/04/11 Publications récentes
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.
thumbnail
darren rose, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Regular Member Publications: 215 Date d'inscription: 04/04/15 Publications récentes
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.
thumbnail
Andrew Jardine, modifié il y a 7 années.

RE: LR62.CEGA6 UserScreenNameException with ø

Liferay Legend Publications: 2416 Date d'inscription: 22/12/10 Publications récentes
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?