Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-16479

"undefined" error message when updating User Status

XMLWordPrintable

      I tried to save a User status update and saw an error in red : "There was an error - undefined".

        1. status_entry_fail.png
          status_entry_fail.png
          57 kB
        2. there was an error - undefined.png
          there was an error - undefined.png
          19 kB

            [CONFSERVER-16479] "undefined" error message when updating User Status

            Don Willis added a comment -

            So the error message is:

            • Too long to fit in the dialog's error pane
            • Confusing, since re-submitting the form does not help.

            I'm going to fix this by adding a response header to state the validity of the xsrf token so that the front-end can provide specific error handling when appropriate. In this case I'll provide a shorter message: "Setting your status failed. Refresh the page."

            The poor handling of long errors by the dialog is trickier and I'll raise an issue in AUI if one doesn't exist.

            Don Willis added a comment - So the error message is: Too long to fit in the dialog's error pane Confusing, since re-submitting the form does not help. I'm going to fix this by adding a response header to state the validity of the xsrf token so that the front-end can provide specific error handling when appropriate. In this case I'll provide a shorter message: "Setting your status failed. Refresh the page." The poor handling of long errors by the dialog is trickier and I'll raise an issue in AUI if one doesn't exist.

            David Taylor (Inactive) added a comment -
            The error handling on the front-end just doesn't handle it properly.

            (Dammit, where's my JIRA macro browser?)

            Yes. I should wrap our AJAX calls in a helper that looks for actionErrors, fieldErrors et al and puts the error message in a standard location. And the part we said about being able to re-submit the form, JIRA style. Has the makings of a thankless 20% project : )

            David Taylor (Inactive) added a comment - The error handling on the front-end just doesn't handle it properly. (Dammit, where's my JIRA macro browser?) Yes. I should wrap our AJAX calls in a helper that looks for actionErrors, fieldErrors et al and puts the error message in a standard location. And the part we said about being able to re-submit the form, JIRA style. Has the makings of a thankless 20% project : )

            Don Willis added a comment -

            Yup. This definitely occurs when the anti-XSRF token has expired. The JSON result of the update action even contains the error message: 

             
{"actionErrors":["Your session has expired. You may need to re-submit the form or reload the page."]}

            The error handling on the front-end just doesn't handle it properly.

            Don Willis added a comment - Yup. This definitely occurs when the anti-XSRF token has expired. The JSON result of the update action even contains the error message: {"actionErrors":["Your session has expired. You may need to re-submit the form or reload the page."]} The error handling on the front-end just doesn't handle it properly.

            Don Willis added a comment -

            It happens when you try to set your status from a page you loaded a while ago. Some sort of token expiry problem I guess. Very easily reproduced if you are prepared to wait.

            Don Willis added a comment - It happens when you try to set your status from a page you loaded a while ago. Some sort of token expiry problem I guess. Very easily reproduced if you are prepared to wait.

            Per Fragemann [Atlassian] added a comment -

            I haven't heard any further reports, so it could have been anything: network issue, cluster issue, loadbalancer, garbage collection etc etc. It doesn't really matter, can't reproduce and therefor won't fix now

            Per Fragemann [Atlassian] added a comment - I haven't heard any further reports, so it could have been anything: network issue, cluster issue, loadbalancer, garbage collection etc etc. It doesn't really matter, can't reproduce and therefor won't fix now

            David Taylor (Inactive) added a comment -

            We haven't investigated at all yet, so I can't say that we can't reproduce it. At the very least we might start off by looking by looking at how the error message is constructed and search for errors in the EAC logs.

            David Taylor (Inactive) added a comment - We haven't investigated at all yet, so I can't say that we can't reproduce it. At the very least we might start off by looking by looking at how the error message is constructed and search for errors in the EAC logs.

            Per Fragemann [Atlassian] added a comment -

            If we can't reproduce it, should we resolve as "can't reproduce"?

            Per Fragemann [Atlassian] added a comment - If we can't reproduce it, should we resolve as "can't reproduce"?

            Anatoli added a comment -

            I suspect the problem may be also applicable to 3.0 - there was no development in this area in 3.1 as far as I know.

            Anatoli added a comment - I suspect the problem may be also applicable to 3.0 - there was no development in this area in 3.1 as far as I know.

              Unassigned Unassigned
              dtaylor David Taylor (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: