PUBLIC - Liferay Portal Community Edition

MB Portlet file attachments with non-ascii characters

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 6.1.1 CE GA2
  • Fix Version/s: 6.1.1 CE GA2
  • Component/s: Collaboration > Message Boards
  • Labels:
    None
  • Environment:
    Ubuntu Server 10.04, Tomcat 7.0.27, Liferay 6.1.1 CE GA2
  • Similar Issues:
    Show 4 results 

Description

When attaching files with non-ascii characters in the filename, the following exception is thrown:

message_boards/message/554717?p_p_auth=QMKQ4g4N generates exception: javax.servlet.ServletException: com.liferay.portlet.documentlibrary.FileNameException: /messageboards/554718/554717/filename_???.docx
13:52:42,597 ERROR [ajp-bio-8009-exec-1376][IncludeTag:154] com.liferay.portlet.documentlibrary.FileNameException: /messageboards/554718/554717/filename_???.docx
at com.liferay.portlet.documentlibrary.store.DLStoreImpl.validate(DLStoreImpl.java:535)
at com.liferay.portlet.documentlibrary.store.DLStoreImpl.getFileSize(DLStoreImpl.java:290)
at com.liferay.portlet.documentlibrary.store.DLStoreUtil.getFileSize(DLStoreUtil.java:462)

The actual filename is "filename_åäö.docx". As you can see above, the swedish characters "å, ä and ö", have been replaced by questionsmarks. The end user gets a "success" message but rendering of the message breaks and links for removing or editing the message are missing.

Setting priority "Major" since our users extensively use swedish characters in filenames and while instructing them to use only ascii or using Related Assets (uploading works through Documents And Media portlet), it's a major usability problem for our users.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Thomas Berg added a comment -

Just noticed the same problem exists with Wiki attachments

Show
Thomas Berg added a comment - Just noticed the same problem exists with Wiki attachments
Hide
Permalink
Thomas Berg added a comment -

This issue can be closed since this has nothing to do with Liferay.
A reboot of our production server (rather than a restart of Tomcat) led to a missing LANG variable for the java process which caused this issue.

To prevent this from happening again, we just needed to add export LANG="sv_SE.UTF-8" to our startup script.

Show
Thomas Berg added a comment - This issue can be closed since this has nothing to do with Liferay. A reboot of our production server (rather than a restart of Tomcat) led to a missing LANG variable for the java process which caused this issue. To prevent this from happening again, we just needed to add export LANG="sv_SE.UTF-8" to our startup script.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    32 weeks, 2 days ago