Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-1970

Ajax exception raised when performing an action after session has been invalidated + implement an AJAX ping cmd when session expires from within an open engine.

Details

    • Bug
    • Resolution: Done
    • Major
    • WCM 5.0 SP3, xCM 6.0.0
    • WCM 5.0 SP2
    • None

    Description

      502 r17398

      I have clicked on a directory in FM in order to refresh it, but my session had been invalidated (see JAHIA-1969 ). So an error message is displayed in a popup.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              [JAHIA-1970] Ajax exception raised when performing an action after session has been invalidated + implement an AJAX ping cmd when session expires from within an open engine.

              Resolved in the JAHIA-2066
              Ajax keep alive call added into the engine window to send a keep alive request to the server each (sessionTimeout/2)

              shyrkov Sergiy Shyrkov (Inactive) added a comment - Resolved in the JAHIA-2066 Ajax keep alive call added into the engine window to send a keep alive request to the server each (sessionTimeout/2)

              Could you check the correct behaviour of AJAX action menus or navigation (in the AJAX File Manager or in the sitemap) when the user session expires? (putting a session to 2-3 minutes should definitively help trying to test all the use case for such a bug - the idea is to try to avoid exception if the editor takes a phone call or goes to a meeting and comes back afterwards with his engine or his edit mode still opens and then tries to access to some action menus or to click with some sitemaps. In such a case it would be great if we could redirect the user to the live mode (or if the page is only available in edit mode or with some permissions to the closer parent page with some guest access (or to the home page of the site)) or close the current engine and redirect the user to the live mode.

              Another think we were speaking about is to implement a small AJAX refresh option within all the edition engines. So basically just a ping from the current user one minutes before the session expires if there is a pop-up engines opened. Most of the editors are telling us they are loosing some content because of the inadequate expiration of the session. This is especially the case when you work on a big text. Sometimes it may take much more than 30 minutes in order to write your big text... and you have no option to see that your session will expire... and when clicking on ok, you loose your session with your whole text! Quite a shame! So we definitevely need to implement something better.

              scroisier Stephane Croisier (Inactive) added a comment - Could you check the correct behaviour of AJAX action menus or navigation (in the AJAX File Manager or in the sitemap) when the user session expires? (putting a session to 2-3 minutes should definitively help trying to test all the use case for such a bug - the idea is to try to avoid exception if the editor takes a phone call or goes to a meeting and comes back afterwards with his engine or his edit mode still opens and then tries to access to some action menus or to click with some sitemaps. In such a case it would be great if we could redirect the user to the live mode (or if the page is only available in edit mode or with some permissions to the closer parent page with some guest access (or to the home page of the site)) or close the current engine and redirect the user to the live mode. Another think we were speaking about is to implement a small AJAX refresh option within all the edition engines. So basically just a ping from the current user one minutes before the session expires if there is a pop-up engines opened. Most of the editors are telling us they are loosing some content because of the inadequate expiration of the session. This is especially the case when you work on a big text. Sometimes it may take much more than 30 minutes in order to write your big text... and you have no option to see that your session will expire... and when clicking on ok, you loose your session with your whole text! Quite a shame! So we definitevely need to implement something better.

              People

                shyrkov Sergiy Shyrkov (Inactive)
                dsaulnier_old Damien Saulnier
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases

                      Packages

                        Version Package
                        WCM 5.0 SP3
                        xCM 6.0.0