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

As a 5.x User I expect better info when I lack access to content

    Details

      Description

      I created a new section and affected it to a node.

      In my website, when I'm not connected, if I try to see this page, Symfony throws an exception :

      "User does not have access to 'read' 'content'
      500 Internal Server Error - UnauthorizedException"

      Surprising. I think this exception should be caught by default to display a login form. This works if I set legacy_mode to true for my siteaccess. I would prefer not to do this.
      How can I catch this exception to display my login form or register form ? What is the best practice in eZ 5 ?

      I tried my problem in "prod mode". The exception is still displayed, but seems to be caught by twig :

      "TwigBundle:Exception:error500.html.twig"

      Also described here : http://share.ez.no/forums/ez-publish-5-platform/user-does-not-have-access-to-read-content/

        Issue Links

          Activity

          Nicolas Lescure created issue -
          Nicolas Lescure made changes -
          Field Original Value New Value
          Affects Version/s 2013.1 [ 11679 ]
          Nicolas Lescure made changes -
          Description I created a new section and affected it to a node.

          In my website, when I'm not connected, if I try to see this page, Symfony throws an exception :

          User does not have access to 'read' 'content'

          500 Internal Server Error - UnauthorizedException

          Surprising. I think this exception should be caught by default to display a login form. This works if I set legacy_mode to true for my siteaccess. I would prefer not to do this.

          How can I catch this exception to display my login form or register form ? What is the best practice in eZ 5 ?

          I tried my problem in "prod mode". The exception is still displayed, but seems to be caught by twig :

          TwigBundle:Exception:error500.html.twig



          Also described here : http://share.ez.no/forums/ez-publish-5-platform/user-does-not-have-access-to-read-content/
          I created a new section and affected it to a node.

          In my website, when I'm not connected, if I try to see this page, Symfony throws an exception :

          "User does not have access to 'read' 'content'
          500 Internal Server Error - UnauthorizedException"

          Surprising. I think this exception should be caught by default to display a login form. This works if I set legacy_mode to true for my siteaccess. I would prefer not to do this.
          How can I catch this exception to display my login form or register form ? What is the best practice in eZ 5 ?

          I tried my problem in "prod mode". The exception is still displayed, but seems to be caught by twig :

          "TwigBundle:Exception:error500.html.twig"


          Also described here : http://share.ez.no/forums/ez-publish-5-platform/user-does-not-have-access-to-read-content/
          Jérôme Vieilledent (Inactive) made changes -
          Labels login security
          Fix Version/s Engineering tracked issues [ 11179 ]
          Fix Version/s Aconcagua [ 11281 ]
          Affects Version/s 2013.4 [ 12082 ]
          Affects Version/s 5.1 [ 11280 ]
          Affects Version/s 2013.1 [ 11679 ]
          André Rømcke made changes -
          Status Open [ 1 ] Backlog [ 10000 ]
          André Rømcke made changes -
          Summary User does not have access to 'read' 'content' As a User I would expect 5.x to display better info when I lack access to content
          André Rømcke made changes -
          Issue Type Bug [ 1 ] Story [ 7 ]
          André Rømcke made changes -
          Summary As a User I would expect 5.x to display better info when I lack access to content As a 5.x User I expect better info when I lack access to content
          André Rømcke made changes -
          Rank Ranked higher
          André Rømcke made changes -
          Link This issue is duplicated by EZP-20043 [ EZP-20043 ]
          André Rømcke made changes -
          Link This issue relates to EZP-19786 [ EZP-19786 ]
          Paulo Nunes (Inactive) made changes -
          Fix Version/s QA tracked issues [ 11072 ]
          Pedro Resende (Inactive) made changes -
          Link This issue relates to EZP-20844 [ EZP-20844 ]
          André Rømcke made changes -
          Affects Version/s 5.0 [ 10300 ]
          Affects Version/s Known Issues 5.x Stack [ 11285 ]
          André Rømcke made changes -
          Link This issue relates to EZP-21297 [ EZP-21297 ]
          André Rømcke made changes -
          Comment [ EDIT: forget about that and delete this...

          ]
          André Rømcke made changes -
          Rank Ranked higher
          André Rømcke made changes -
          Rank Ranked higher
          André Rømcke made changes -
          Epic Link PM-76 [ 32636 ]
          André Rømcke made changes -
          Fix Version/s 5.2-alpha1 [ 11281 ]
          André Rømcke made changes -
          Epic Link PM-76 [ 32636 ] PM-77 [ 32648 ]
          André Rømcke made changes -
          Component/s DemoBundle [ 11642 ]
          Component/s Symfony stack [ 10303 ]
          Hide
          Jérôme Vieilledent (Inactive) added a comment -

          Hi

          You can do 2 things:

          The exception adds more granularity.

          Show
          Jérôme Vieilledent (Inactive) added a comment - Hi You can do 2 things: Customize the error pages Implement an exception listener . The exception adds more granularity.
          Joaquim Cavalleri (Inactive) made changes -
          Link This issue relates to EZP-21955 [ EZP-21955 ]
          André Rømcke made changes -
          Rank Ranked higher
          André Rømcke made changes -
          Rank Ranked lower
          André Rømcke made changes -
          Workflow eZ Engineering Scrumban Workflow [ 53484 ] EZ* Development Workflow [ 69627 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 69627 ] EZEE Development Workflow [ 107933 ]
          Alex Schuster made changes -
          Workflow EZEE Development Workflow [ 107933 ] EZEE and EZP Story Workflow [ 127114 ]
          Hide
          Sylvain Guittard added a comment -

          Closing this issue, because it relates to 5.x (not supported) and Symfony provides a way to override the error pages.

          Show
          Sylvain Guittard added a comment - Closing this issue, because it relates to 5.x (not supported) and Symfony provides a way to override the error pages.
          Sylvain Guittard made changes -
          Status Backlog [ 10000 ] Closed [ 6 ]
          Resolution Obsolete [ 8 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Backlog Backlog
          9d 22h 47m 1 André Rømcke 06/May/13 5:10 PM
          Backlog Backlog Closed Closed
          1744d 7h 42m 1 Sylvain Guittard 13/Feb/18 11:53 PM

            People

            • Assignee:
              Unassigned
              Reporter:
              Nicolas Lescure
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: