Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #12531 (closed)

Opened 10 years ago

Closed 10 years ago

BUG: cannot attach pdf in Web

Reported by: pwalczysko Owned by: web-team@…
Priority: blocker Milestone: 5.1.0-m1
Component: Web Version: 5.0.3
Keywords: n.a. Cc: ux@…, sbesson
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

On octopus, cannot attach .pdf file in Web (insight is fine).
Workflow:

  • login as any user
  • go to right hand pane and try to attach a .pdf file to a Project or Dataset or Image
  • when Attachment dialog pops up, select Choose file
  • have a ready .pdf document locally, browse to it, select and
  • hit Accept in the dialog
  • a message from the browser says Undefined - the action does not proceed - see screenshot

Note: Not browser-specific, because occurs in Safari and Firefox.
Note: Not name -specific, because occurs even with PDF files which were renamed to have suffix .txt -> attaching these files fails as well

Attachments (1)

Screen Shot 2014-08-20 at 11.34.23.png (23.3 KB) - added by pwalczysko 10 years ago.

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by pwalczysko

comment:1 Changed 10 years ago by pwalczysko

Additional info: when another type of PDF is used (the type created by OMERO.figure - the attachment action is performed just fine.
Workflow:

  • create a .pdf using OMERO.figure on Nightshade
  • download this .pdf locally
  • login to octopus and try to attach this nightshade-OMERO.figure-created .pdf to a dataset on octopus
  • action proceeds with no problem

Note that the PDF files mentioned in the header of this ticket are coming from one-help repository.

comment:2 Changed 10 years ago by jburel

  • Milestone changed from 5.0.4 to 5.1.0-m1

Moving to 5.1.0-m1

comment:3 Changed 10 years ago by bpindelski

This is most likely caused by the PDF exceeding a size limitation - trying to upload cls-public.pdf, which is 3.1 MB in size, results in an HTTP 413 Request entity too large return code. I guess the web client (or Django) limit the size of uploaded PDF files.

comment:4 Changed 10 years ago by atarkowska

@bpindelski nginx config is missing

    sendfile on;
    send_timeout 60s;
    client_max_body_size 0;
Last edited 10 years ago by atarkowska (previous) (diff)

comment:5 Changed 10 years ago by bpindelski

@atarkowska: I see. Is it worth adding that part to the nginx template? And also checking if the Apache template will need similar settings?

comment:7 Changed 10 years ago by bpindelski

  • Resolution set to invalid
  • Status changed from new to closed

Closing, since this was a configuration issue and not a fault in the code.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.65966 sec.)

We're Hiring!