[MAGNOLIA-2063] Files with Apostrophes in the Name Cannot Be Uploaded to Rich Editor Paragraph Created: 18/Feb/08  Updated: 23/Jan/13  Resolved: 14/Jul/08

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.5.4
Fix Version/s: 3.6, 3.5.9

Type: Bug Priority: Minor
Reporter: Sean McMains Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File revision2637.diff    
Issue Links:
relation
is related to MAGNOLIA-2259 Handle special characters properly wh... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When uploading a file attachment to a rich editor paragraph, the upload fails if the filename contains an apostrophe:

1. Create a new Rich Editor Paragraph
2. Enter some sample text.
3. Select a word. Click the "link" button.
4. Click the upload tab.
5. Click "browse." Select a file with an apostrophe in the filename.
6. Click upload.

Expected behavior:
File should upload normally, just like any other file.

Actual behavior:
Browser throws a javascript error, and the file is not uploaded.



 Comments   
Comment by Sean McMains [ 18/Feb/08 ]

Here's a diff that gets past the initial javascript errors, and which seems to get things working ok.

When one saves the dialog, there are a few errors in the log files claiming that jackrabbit thinks the filename is illegal, but as far as I can tell, everything still works just fine.

Comment by Magnolia International [ 08/Jul/08 ]

Patch applied on both the 3.5 branch and the trunk (3.6), thanks !

  • will check what the jackrabbit warnings are about.
Comment by Magnolia International [ 14/Jul/08 ]

I could reproduce the exception. This happens when checking/parsing/resolving links, but has no apparent impact at the moment. Will fix this properly with MAGNOLIA-2259

Generated at Mon Feb 12 03:33:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.