Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Medium Medium
    • Resolution: Unresolved
    • Affects Version/s: 4.3.0
    • Fix Version/s: None
    • Labels:
      None
    • Environment:

      eZ Publish 4.3

      Description

      With a classic install in cluster mode using the ezdfs documentation : when uploading an image through ezoe there is a fatal error.

        Activity

        Hide
        André R added a comment -

        I'll guess you have same issue when you use ezmultiupload and relations upload(bottom of edit screen in admin interface)?

        Show
        André R added a comment - I'll guess you have same issue when you use ezmultiupload and relations upload(bottom of edit screen in admin interface)?
        Hide
        Matthieu Sévère added a comment -

        No both are working fine ..
        Note that the upload through ezoe ends up with a fatal error but the uploaded worked (the file is in the media library)

        Show
        Matthieu Sévère added a comment - No both are working fine .. Note that the upload through ezoe ends up with a fatal error but the uploaded worked (the file is in the media library)
        Hide
        André R added a comment -

        In reply to comment #064628
        Ok, do you have the error as well?? A bit more useful.

        Show
        André R added a comment - In reply to comment #064628 Ok, do you have the error as well?? A bit more useful.
        Hide
        Matthieu Sévère added a comment -

        No both (ezmultiupload and object relation upload) are working fine : no error.

        The error is when uploading a new image in ezoe there is a fatal error that prevent the contributor to go to next step (choose image properties) but after checking the image is well uploaded..

        Please note that the exact same problem is happening whith file upload. (probably use the same code thus)

        Show
        Matthieu Sévère added a comment - No both (ezmultiupload and object relation upload) are working fine : no error. The error is when uploading a new image in ezoe there is a fatal error that prevent the contributor to go to next step (choose image properties) but after checking the image is well uploaded.. Please note that the exact same problem is happening whith file upload. (probably use the same code thus)
        Hide
        André R added a comment -

        In reply to comment #064630
        I was talking about upload via ezoe, you say it ends in fatal error, so I'm asking about the error(s) you get when that fatal error happens.

        Show
        André R added a comment - In reply to comment #064630 I was talking about upload via ezoe, you say it ends in fatal error, so I'm asking about the error(s) you get when that fatal error happens.
        Hide
        Matthieu Sévère added a comment -

        In reply to comment #064631
        Oh ok. I have nothing in logs ...

        Show
        Matthieu Sévère added a comment - In reply to comment #064631 Oh ok. I have nothing in logs ...
        Hide
        André R added a comment -

        No other users have reported this and not enough info provided so please reopen if more info is available or others can reproduce it.

        Show
        André R added a comment - No other users have reported this and not enough info provided so please reopen if more info is available or others can reproduce it.
        Hide
        Bjørnar Helland added a comment -

        Hi

        We are experiencing the same problem. eZ version 4.6, and ezoe 5.3.0

        When we upload a file through the "Insert/edit object" button, we get a "PHP Fatal error: Call to a member function attribute() on a non-object". This happens in line 124 in /modules/ezoe/upload.php.

        123: $newVersionObject = $newObject->attribute( 'current' );
        124: $newObjectDataMap = $newVersionObject->attribute('data_map');

        The $newVersionObject is null. This happens in about 19 of 20 times, but only in our extension and not in the eZ admin, and it only happens in cluster mode with ezdfs.

        Show
        Bjørnar Helland added a comment - Hi We are experiencing the same problem. eZ version 4.6, and ezoe 5.3.0 When we upload a file through the "Insert/edit object" button, we get a "PHP Fatal error: Call to a member function attribute() on a non-object". This happens in line 124 in /modules/ezoe/upload.php. 123: $newVersionObject = $newObject->attribute( 'current' ); 124: $newObjectDataMap = $newVersionObject->attribute('data_map'); The $newVersionObject is null. This happens in about 19 of 20 times, but only in our extension and not in the eZ admin, and it only happens in cluster mode with ezdfs.
        Hide
        Luca Realdi added a comment -

        Same issue in ez2014.11 ezdfs on apache.
        The log is

        [Wed May 20 16:05:47 2015] [error] [client 77.72.198.133] PHP Warning: POST Content-Length of 16436960 bytes exceeds the limit of 8388608 bytes in Unknown on line 0, referer: http://tcu.opencontent.it/backend/ezoe/upload/495433/1/objects/

        [Wed May 20 16:06:46 2015] [error] [client 77.72.198.133] PHP Fatal error: Call to a member function currentVersion() on a non-object in /home/httpd/tcu.opencontent.it/html/ezpublish_legacy/extension/ezoe/modules/ezoe/upload.php on line 123, referer: http://tcu.opencontent.it/backend/ezoe/upload/495433/1/objects/

        it would seem that it is not fired and catched the http error UPLOAD_ERR_FORM_SIZE

        Show
        Luca Realdi added a comment - Same issue in ez2014.11 ezdfs on apache. The log is [Wed May 20 16:05:47 2015] [error] [client 77.72.198.133] PHP Warning: POST Content-Length of 16436960 bytes exceeds the limit of 8388608 bytes in Unknown on line 0, referer: http://tcu.opencontent.it/backend/ezoe/upload/495433/1/objects/ [Wed May 20 16:06:46 2015] [error] [client 77.72.198.133] PHP Fatal error: Call to a member function currentVersion() on a non-object in /home/httpd/tcu.opencontent.it/html/ezpublish_legacy/extension/ezoe/modules/ezoe/upload.php on line 123, referer: http://tcu.opencontent.it/backend/ezoe/upload/495433/1/objects/ it would seem that it is not fired and catched the http error UPLOAD_ERR_FORM_SIZE

          People

          • Assignee:
            unknown
            Reporter:
            Matthieu Sévère
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: