Bug 1033493 - Fail to upload file on drupal when creating content on community
Summary: Fail to upload file on drupal when creating content on community
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 08:46 UTC by Tian Feng
Modified: 2015-05-15 01:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-30 00:50:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tian Feng 2013-11-22 08:46:36 UTC 
Description of problem:
Go to community as admin. Tried to upload valid pdf/txt/odc/doc/png/jpeg file on drupal when creating content. Fail to do it for meeting "The selected file 1.pdf could not be uploaded. The anti-virus scanner was not able to check the file. The file cannot be uploaded."

Version-Release number of selected component (if applicable):
devenv-stage_582
devenv_4061

How reproducible:
Always

Steps to Reproduce:
1. Go to community as admin
2. Tried to upload file when creating content
3. 

Actual results:
Fail to upload file and meet "The selected file 1.pdf could not be uploaded. The anti-virus scanner was not able to check the file. The file cannot be uploaded."

Expected results:
Should upload file successfully.

Additional info:
Comment 1 Tian Feng 2014-01-07 02:57:56 UTC 
Go to /admin/build/modules/list and unchecking ClamAV Anti-Virus scrolling to the bottom and clicking save. Then it can upload file successfully.
Comment 2 Fabiano Franz 2014-01-21 21:26:48 UTC 
Fixed right in prod.
Comment 3 Yujie Zhang 2014-01-22 07:04:58 UTC 
Tested on devenv_4256, the file can be uploaded successfully after unchecking Anti-Virus option now, so verify this bug, thanks.
Note You need to log in before you can comment on or make changes to this bug.