Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files that are uploaded inside of custom Content Types that have 'funky' file names aren't being assigned a data_file_path in the db #700

Open
briancsinger opened this issue Mar 6, 2014 · 0 comments
Labels

Comments

@briancsinger
Copy link

The test that raised this issue was when I uploaded a pdf with a filename like pdf_name.here.pdf

When I then try to open this file it gets truncated to pdf_name.here, which doesn't exist.

I checked the cms_attachments table and the new record wasn't assigned a data_file_path like content that's uploaded as a File.

Scrubbing the filename to 'pdf_name.pdf' fixes the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant