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

async publishing: the polling javascript can get mixed-up and give bad results

    Details

      Description

      Reproduced on Chrome, might happen on other browsers as well:

      1. added to the async publication two sleep (30) calls, just before and after object publication, to simulate a long-publication event
      2. tail -f | grep the apache access log, to see incoming requests
      2. send an object to publish
      3. open 2 more tabs, on the same url: ezflow_site_admin/content/queued/149/14
      4. verify that 3 ajax requests per second come in
      5. what happens at the end: when object was published, tabs 2 and 3 stopped polling, and showed link to published object, while tab 1 did not and kept going on

      Note that I did not reproduce it, but a customer has problems where sometimes the opposite happens: a page stops polling for a time going up to 30 minutes, leading the editor to think that a page is not published when it really is

      1. pic_ok.png
        64 kB
      2. pic.png
        31 kB

        Issue Links

          Activity

          Hide
          Pedro Resende (Inactive) added a comment -

          Tested and approved by Q.A.

          Show
          Pedro Resende (Inactive) added a comment - Tested and approved by Q.A.
          Show
          Yannick Roger (Inactive) added a comment - - edited Fixed in master: https://github.com/ezsystems/ezpublish-legacy/commit/72b677ac7db624dd2635bad3fd4d072b89e81af5 https://github.com/ezsystems/ezpublish-legacy/commit/ce59725504c3a2c83aacc72b6c1105289f80d23e https://github.com/ezsystems/ezpublish-legacy/commit/54892d128ae4b653615b473ca4e32e6a407fd104 https://github.com/ezsystems/ezpublish-legacy/commit/097977ff8324fce5f3769aa8c956dd3527eb2760 https://github.com/ezsystems/ezpublish-legacy/commit/1f54b6251a85c3c85e41ece43f35421de9fc0bdb
          Show
          Damien Pobel (Inactive) added a comment - PR: https://github.com/ezsystems/ezpublish-legacy/pull/1048
          Hide
          Gaetano Giunta (Inactive) added a comment -

          Apart from fixing the cases where the polling stops working because of javascript problems, I think that it is important to give feedback to the editor if the polling fails for any reason, such as e.g. network errors, so that he can try reloading the page or taking other corrective action.

          F.e. showing the timestamp of the last succesfull check done via javascript, or displaying a warning message when polling gets back unexpected responses

          Show
          Gaetano Giunta (Inactive) added a comment - Apart from fixing the cases where the polling stops working because of javascript problems, I think that it is important to give feedback to the editor if the polling fails for any reason, such as e.g. network errors, so that he can try reloading the page or taking other corrective action. F.e. showing the timestamp of the last succesfull check done via javascript, or displaying a warning message when polling gets back unexpected responses

            People

            • Assignee:
              Unassigned
              Reporter:
              Gaetano Giunta (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              6 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 - 5 hours
                5h