Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27214

Disaperance of the edit|trash icons in the multi file upload file list

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: High High
    • Resolution: Fixed
    • Affects Version/s: 1.9.0-beta1
    • Fix Version/s: QA tracked issues
    • Environment:

      Operating System: Debian 8
      PHP Version: 5.6.30-0+deb8u1
      Database and version: Mysql 5.5.54-0+deb8u1
      Browser (and version): Firefox 52
      Env: Prod

      Description

      There are some situations where the edit|trash icons in the multi file upload file list disapear.
      The steps below are not 100% sure to make the issue appear, but are the steps I was able to reproduce this behavior most of times.

      Steps to Reproduce

      -go to ezplatform landing page
      -(the next two steps must be done in a quick sequence)
      -Drag&Drop a big file into multi file upload area
      -while the file it's uploading, drag&drop another one into multi file upload

      the edit|trash icons of the first one do not appear anylonger

      Edit: When the error happens, I have in developer tools

      TypeError: event.target is undefined[Learn More]  _ezcombo:1683:1
      	Y.mfu.FileItemView<._showFileUploadError http://ezp60.local/_ezcombo:1683:1
      	bound  self-hosted:915:17
      	Y.mfu.Plugin.FileUploadService<._attemptToPublishContent http://ezp60.local/_ezcombo:2347:17
      	bound  self-hosted:1002:17
      	XmlHttpRequestConnection.prototype.execute/XHR.onreadystatechange http://ezp60.local/_ezcombo:1634:17
      

        Issue Links

          Activity

          Hide
          Paulo Nunes (Inactive) added a comment -

          Did the same actions on Ubuntu 15.10 (with php 5.6) and also had a POST error with response

          <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
          <html><head>
          <title>413 Request Entity Too Large</title>
          </head><body>
          <h1>Request Entity Too Large</h1>
          The requested resource<br />/api/ezp/v2/content/objects<br />
          does not allow request data with POST requests, or the amount of data provided in
          the request exceeds the capacity limit.
          <hr>
          <address>Apache/2.4.12 (Ubuntu) Server at ezp60.local Port 80</address>
          </body></html>
          {"ErrorMessage":{"_media-type":"application\/vnd.ez.api.ErrorMessage+json","errorCode":400,"errorMessage":"Bad Request","errorDescription":"Missing or invalid 'LocationCreate' element for ContentCreate."}}
          

          Show
          Paulo Nunes (Inactive) added a comment - Did the same actions on Ubuntu 15.10 (with php 5.6) and also had a POST error with response <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>413 Request Entity Too Large</title> </head><body> <h1>Request Entity Too Large</h1> The requested resource<br />/api/ezp/v2/content/objects<br /> does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. <hr> <address>Apache/2.4.12 (Ubuntu) Server at ezp60.local Port 80</address> </body></html> {"ErrorMessage":{"_media-type":"application\/vnd.ez.api.ErrorMessage+json","errorCode":400,"errorMessage":"Bad Request","errorDescription":"Missing or invalid 'LocationCreate' element for ContentCreate."}}
          Show
          Piotr Nalepa (Inactive) added a comment - PR created: https://github.com/ezsystems/ezplatform-multi-file-upload/pull/18
          Hide
          Paulo Nunes (Inactive) added a comment -

          Using https://github.com/ezsystems/ezplatform-multi-file-upload/pull/18, when I upload a 51 Mb file, I have the Unexpected error notification. In the POST response I also have

          <html><head>
          <title>413 Request Entity Too Large</title>
          </head><body>
          <h1>Request Entity Too Large</h1>
          The requested resource<br />/api/ezp/v2/content/objects<br />
          does not allow request data with POST requests, or the amount of data provided in
          the request exceeds the capacity limit.
          <hr>
          <address>Apache/2.4.12 (Ubuntu) Server at ezp60.local Port 80</address>
          </body></html>
          {"ErrorMessage":{"_media-type":"application\/vnd.ez.api.ErrorMessage+json","errorCode":400,"errorMessage":"Bad Request","errorDescription":"Missing or invalid 'LocationCreate' element for ContentCreate."}}
          

          Accordingly development team, the Unexpected error notification is to be expected. Same for the POST response.

          ping Supriya Bhargava: can you please confirm that this is the expected behavior? Thank you

          cc [~piotr.nalepa@ez.no]

          Show
          Paulo Nunes (Inactive) added a comment - Using https://github.com/ezsystems/ezplatform-multi-file-upload/pull/18 , when I upload a 51 Mb file, I have the Unexpected error notification. In the POST response I also have <html><head> <title>413 Request Entity Too Large</title> </head><body> <h1>Request Entity Too Large</h1> The requested resource<br />/api/ezp/v2/content/objects<br /> does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit. <hr> <address>Apache/2.4.12 (Ubuntu) Server at ezp60.local Port 80</address> </body></html> {"ErrorMessage":{"_media-type":"application\/vnd.ez.api.ErrorMessage+json","errorCode":400,"errorMessage":"Bad Request","errorDescription":"Missing or invalid 'LocationCreate' element for ContentCreate."}} Accordingly development team, the Unexpected error notification is to be expected. Same for the POST response. ping Supriya Bhargava : can you please confirm that this is the expected behavior? Thank you cc [~piotr.nalepa@ez.no]

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Nunes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: