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

Image Objects are not correctly displayed in ezflow

    Details

      Description

      Image objects are not displayed when trying to access them through the front-end (i.e: ezflow), and showing unexpected behavior when caches are cleared.

      Scenario 1:

      • Create a folder, and within it an Image object in the admin interface
      • Verify that you can view it by accessing the image, still in the admin interface
      • Go to the front-end, i.e, ezflow
      • Access the folder wherein you created the Image, verify that you can see its thumbnail
      • Access the Image, verify that you cannot see the image

      Scenario 2:

      • Create the folder and Image object as you did in the previous scenario
      • In the front-end, access the folder wherein you created the Image
      • Through the terminal, clear all caches
      • Refresh the page, the thumbnails will now be gone *

      * The image is visible again only if, through the admin interface, you edit the Image object, and then discard the draft

      There are zero errors or notices (apache logs, symfony logs/debugger (using index_dev), ezpublish-legacy logs, Firebug & Chrome dev-tools); everything works as expected by bypassing symfony and accessing the ezpublish_legacy directory directly.

        Activity

        Filipe Dobreira (Inactive) created issue -
        Filipe Dobreira (Inactive) made changes -
        Field Original Value New Value
        Summary Image Objects are not correctly displayed Image Objects are not correctly displayed in ezflow
        Filipe Dobreira (Inactive) made changes -
        Description Image objects are not displayed when trying to access them through the front-end (i.e: ezflow), and showing unexpected behavior when caches are cleared.

        Scenario 1:
         - Create a folder, and within it an Image object in the admin interface
         - Verify that you can view it by accessing the image, still in the admin interface
         - Go to the front-end, i.e, ezflow
         - Access the folder wherein you created the Image, verify that you can see its thumbnail
         - Access the Image, verify that you cannot see the image

        Scenario 2:
         - Create the folder and Image object as you did in the previous scenario
         - In the front-end, access the folder wherein you created the Image
         - Through the terminal, clear all caches
         - Refresh the page, the thumbnails will now be gone \*


        \* The image is visible again only if, through the admin interface, you edit the Image object, and then discard the draft


        There are zero errors or notices (apache logs, symfony logs/debugger (using index_dev), ezpublish-legacy logs); everything works as expected by bypassing symfony and accessing the ezpublish_legacy directory directly.
        Image objects are not displayed when trying to access them through the front-end (i.e: ezflow), and showing unexpected behavior when caches are cleared.

        Scenario 1:
         - Create a folder, and within it an Image object in the admin interface
         - Verify that you can view it by accessing the image, still in the admin interface
         - Go to the front-end, i.e, ezflow
         - Access the folder wherein you created the Image, verify that you can see its thumbnail
         - Access the Image, verify that you cannot see the image

        Scenario 2:
         - Create the folder and Image object as you did in the previous scenario
         - In the front-end, access the folder wherein you created the Image
         - Through the terminal, clear all caches
         - Refresh the page, the thumbnails will now be gone \*


        \* The image is visible again only if, through the admin interface, you edit the Image object, and then discard the draft


        There are zero errors or notices (apache logs, symfony logs/debugger (using index_dev), ezpublish-legacy logs, Firebug & Chrome dev-tools); everything works as expected by bypassing symfony and accessing the ezpublish_legacy directory directly.
        Vidar Langseid made changes -
        Affects Version/s 5.0 Certification [ 11013 ]
        Affects Version/s QA tracked issues [ 11072 ]
        Vidar Langseid made changes -
        Fix Version/s QA tracked issues [ 11072 ]
        Fix Version/s 5.0 Certification [ 11013 ]
        Vidar Langseid made changes -
        Status Open [ 1 ] Backlog [ 10000 ]
        Vidar Langseid made changes -
        Status Backlog [ 10000 ] InputQ [ 10001 ]
        Vidar Langseid made changes -
        Rank Ranked higher
        Damien Pobel (Inactive) made changes -
        Status InputQ [ 10001 ] Development [ 3 ]
        Assignee Damien Pobel [ damien.pobel@ez.no ]
        Damien Pobel (Inactive) logged work - 30/Oct/12 11:05 AM
        • Time Spent:
          1 hour
           

          trying to reproduce

        Hide
        Damien Pobel (Inactive) added a comment -

        I'm not able to reproduce this issue.

        • Was it tested in a cluster setup ?
        • Could you precise the command line used to clear all caches in the terminal ?
        Show
        Damien Pobel (Inactive) added a comment - I'm not able to reproduce this issue. Was it tested in a cluster setup ? Could you precise the command line used to clear all caches in the terminal ?
        Damien Pobel (Inactive) made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 1 hour [ 3600 ]
        Worklog Id 22368 [ 22368 ]
        Filipe Dobreira (Inactive) made changes -
        Assignee Damien Pobel [ damien.pobel@ez.no ] Filipe Dobreira [ filipe.dobreira@ez.no ]
        Hide
        Filipe Dobreira (Inactive) added a comment -

        @Damien:

        • The issue was reproduced in single-mode, cluster DB and cluster DFS
        • The commands I used were the following:

        $ php app/console cache:clear --env=prod
        $ cd app/ezpublish_legacy && php bin/php/ezcache.php --clear-all --purge

        And also tried simply rm -rf cache/* to clear the Sf cache.

        However, this issue is no longer present in the latest build, so I'm going to close it as fixed.

        Show
        Filipe Dobreira (Inactive) added a comment - @Damien: The issue was reproduced in single-mode, cluster DB and cluster DFS The commands I used were the following: $ php app/console cache:clear --env=prod $ cd app/ezpublish_legacy && php bin/php/ezcache.php --clear-all --purge And also tried simply rm -rf cache/* to clear the Sf cache. However, this issue is no longer present in the latest build, so I'm going to close it as fixed.
        Filipe Dobreira (Inactive) made changes -
        Status Development [ 3 ] Devlopment done [ 5 ]
        Filipe Dobreira (Inactive) made changes -
        Assignee Filipe Dobreira [ filipe.dobreira@ez.no ]
        Status Devlopment done [ 5 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Hide
        Pedro Resende (Inactive) added a comment - - edited

        Just re-tested on today's ttl build #84 and this issue is still present

        Show
        Pedro Resende (Inactive) added a comment - - edited Just re-tested on today's ttl build #84 and this issue is still present
        Pedro Resende (Inactive) made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Vidar Langseid made changes -
        Status Reopened [ 4 ] Backlog [ 10000 ]
        Vidar Langseid made changes -
        Status Backlog [ 10000 ] InputQ [ 10001 ]
        Paulo Nunes (Inactive) made changes -
        Status InputQ [ 10001 ] QA [ 10008 ]
        Assignee Paulo Nunes [ paulo.nunes@ez.no ]
        Paulo Nunes (Inactive) made changes -
        Status QA [ 10008 ] QA done [ 10007 ]
        André Rømcke made changes -
        Assignee Paulo Nunes [ paulo.nunes@ez.no ]
        Status QA done [ 10007 ] Closed [ 6 ]
        Fix Version/s 5.0.0rc1 [ 11080 ]
        Resolution Fixed [ 1 ]
        André Rømcke made changes -
        Workflow eZ Community Workflow [ 34218 ] eZ Engineering Scrumban Workflow [ 48691 ]
        André Rømcke made changes -
        Workflow eZ Engineering Scrumban Workflow [ 48691 ] EZ* Development Workflow [ 83166 ]
        Alex Schuster made changes -
        Workflow EZ* Development Workflow [ 83166 ] EZEE Development Workflow [ 121746 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Backlog Backlog
        5d 28m 1 Vidar Langseid 29/Oct/12 4:21 PM
        InputQ InputQ Development Development
        52m 2s 1 damien.pobel@ez.no 29/Oct/12 5:13 PM
        Development Development Development Done Development Done
        1d 19h 17m 1 Filipe Dobreira (Inactive) 31/Oct/12 12:31 PM
        Development Done Development Done Closed Closed
        20s 1 Filipe Dobreira (Inactive) 31/Oct/12 12:31 PM
        Closed Closed Reopened Reopened
        5d 5h 58m 1 pedro.resende@ez.no 05/Nov/12 6:29 PM
        Reopened Reopened Backlog Backlog
        19h 40m 1 Vidar Langseid 06/Nov/12 2:10 PM
        Backlog Backlog InputQ InputQ
        5s 2 Vidar Langseid 06/Nov/12 2:10 PM
        InputQ InputQ QA QA
        21h 46m 1 Paulo Nunes 07/Nov/12 11:56 AM
        QA QA QA Done QA Done
        16s 1 Paulo Nunes 07/Nov/12 11:56 AM
        QA Done QA Done Closed Closed
        2d 1h 32m 1 André Rømcke 09/Nov/12 1:29 PM

          People

          • Assignee:
            Unassigned
            Reporter:
            Filipe Dobreira (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 hour
              1h