Usernames with quotes and double quotes create a bug in Item Owner field

4 views
Skip to first unread message

Phil -- wbtc.fr --

unread,
Feb 14, 2011, 5:46:17 AM2/14/11
to in-port...@googlegroups.com
Hi,

tested in 512beta1

If we have an user name with a single quote inside it, example Rock'n'Roll, you cannot edit or create an item for this user: you won't be able to save or go to another tab for this item, you'll have a "user not found" error.

If we have an user with double quotes, it doesn't work also, but for another reason: once you select the owner and validate, in the owner field the " is replaced by " .

p

Alexander Obuhovich

unread,
Feb 14, 2011, 7:08:52 AM2/14/11
to in-port...@googlegroups.com
Yes, username isn't validated and we have another discussion about it already. I guess, that we need to do extra escaping of username anywhere to fix that.


--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.



--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

Phil -- wbtc.fr --

unread,
Feb 14, 2011, 8:17:04 AM2/14/11
to in-port...@googlegroups.com
this other discussion is related, but I didn't saw anywhere in the task such problem as the one I'm reporting.


2011/2/14 Alexander Obuhovich <aik....@gmail.com>

Dmitry A.

unread,
Feb 14, 2011, 12:26:33 PM2/14/11
to in-port...@googlegroups.com
Hi Phil,


Thanks for reporting and describing your issue.

While described issue is closely related to the other one from development stand point it makes more sense to address the source of the problem rather them to spend time on workarounds of the current solution.

At this point, we have worked out the solid plan for approaching most of Username related issues (if not all) in this Validation for User Login field discussion and have a task ready. Mostly likely it will go into 5.1.3 release (my suggestion), but patch might be ready before that.

In case if it's super critical to your project, we can give you a temporarily solution when Users won't be able to register with NON alpha-numeric usernames, but it won't be a complete patch for that task since there is more to it.


DA

Alexander Obuhovich

unread,
Mar 13, 2011, 7:46:29 AM3/13/11
to in-port...@googlegroups.com
This doesn't seem to be related to a user login field in particular but to the kLEFTFormatter class being used to process it.

Reply all
Reply to author
Forward
0 new messages