Closed Bug 355994 Opened 18 years ago Closed 16 years ago

alias too long error message is confusing

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

2.20.1
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: timeless, Unassigned)

References

()

Details

I entered "遠藤真美様を担当して頂きます" as my bug alias. Afaik that's 14 characters. but Bugzilla told me that aliases cannot be longer than 20 characters. Hat worn: confused end user who typed 14 glyphs and doesn't understand how that relates to an error message indicating that aliases cannot be longer than 20 characters. Expected results: Error message should clearly explain and indicate how the input fails to match the expectations and suggest input that would match expectations. Actual results: Alias Too Long Bug aliases cannot be longer than 20 characters. Please choose a shorter alias.
ok, that's no fair. i did *not* enter what you see in comment 0!. i entered: "遠藤真美様を担当して頂きます"
Bug 304550 will solve this by making varchar(20) really mean "20 characters" and not "20 bytes." *** This bug has been marked as a duplicate of 304550 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
IIRC length($str) doesn't deal too well with UTF-8 strings such that length($str) > 20 may return false if a UTF-8 string is only 14 chars.
Right, that bug didn't fix it because of how DBI works. The new bug for fixing this globally is bug 363153.
Status: REOPENED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → DUPLICATE
I don't believe this bug is a duplicate of bug 363153 -- this string is coming from the user, not from DBI so I doubt changing the DBI settings is going to help.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
I can confirm that the patch from bug 363153 didn't fix this bug.
Status: REOPENED → ASSIGNED
I can confirm this is fixed in 3.2: https://landfill.bugzilla.org/bugzilla-3.2-branch/show_bug.cgi?id=6999 Not sure if it was 'fixed' by Perl module upgrades along with bug 363153
Okay. So fixed somehow or another in 3.2. :-)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago16 years ago
Resolution: --- → WORKSFORME
This is a Windows* OS/file system issue.The cause is directory paths on the drive is longer than 255 characters (including spaces).There's a lot of additional softwares which can fix this problem like Long Path Tool. http://PathTooDeep.com Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename.
You need to log in before you can comment on or make changes to this bug.