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

After user (group/location) has been trashed, an exception is thrown on login

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: High High
    • Resolution: Fixed
    • Affects Version/s: 5.1
    • Fix Version/s: Customer request
    • Component/s: Platform stack
    • Labels:
      None

      Description

      After editing a user, sending the object parent to trash and restoring it, trying to login in the frontend will result in an exception / HTTP 500 error.

      Steps to reproduce:
      1. Create a user group
      2. Create an user object under this group, and edit it once again (do not specify any image).
      3. Remove the group to trash.
      4. Restore the user/group:
        1. Restore group to original location
        2. Restore user to the (now restored) group location
      5. Login with this user in the frontend

      h5 Result:
      An exception will be thrown:

      Argument '$path' is invalid: Storage directory not found in "user-name"

      Further Notes:

      After "trashing" the user, the image attribute (for the published version 2) on the database seems wrong. instead of empty file, it now contains:

      <?xml version="1.0" encoding="utf-8"?>
      <ezimage serial_number="1" is_valid="" filename="c992d69f74dcf51ff04a051ef0d93d6b." suffix="" basename="c992d69f74dcf51ff04a051ef0d93d6b" dirpath="/trashed" url="/trashed/c992d69f74dcf51ff04a051ef0d93d6b." original_filename="" mime_type="" width="" height="" alternative_text="" alias_key="1293033771" timestamp="1393596398"><original attribute_id="628" attribute_version="1" attribute_language="eng-GB"/></ezimage>
      

      After restoring it:

      <?xml version="1.0" encoding="utf-8"?>
      <ezimage serial_number="1" is_valid="" filename="mem2-mem1." suffix="" basename="mem2-mem1" dirpath="" url="mem2-mem1." original_filename="" mime_type="" width="" height="" alternative_text="" alias_key="1293033771" timestamp="1393596398"><original attribute_id="628" attribute_version="1" attribute_language="eng-GB"/></ezimage>
      

        Issue Links

          Activity

          Hide
          Yannick Roger (Inactive) added a comment -

          Use the fix for EZP-22628 will fix the root cause of the problem.

          Corrupted users can be deleted manually or their ezimage fields can be wiped out in the database.

          Show
          Yannick Roger (Inactive) added a comment - Use the fix for EZP-22628 will fix the root cause of the problem. Corrupted users can be deleted manually or their ezimage fields can be wiped out in the database.

            People

            • Assignee:
              Unassigned
              Reporter:
              Joao Inacio (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: