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

Unresponsive script error when default editor set to Rich Text

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Support Request
    • Icon: Low Low
    • None
    • 3.4
    • None

      We just switched the default editor to Rich text, and now, certain pages give the following error when we try to edit them with Firefox 3.6.13.

      "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

      Script: https://wiki-bsse.ethz.ch/s/2029/7/3/_/download/superbatch/js/batch.js:144"
      If a user's default is "Wiki markup" they can just stop the script and carry on, but in Rich text, there's just a blank pane after stopping the script.

      There's no error in IE8, it works in both Rich text and Wiki markup.

      I also restarted Confluence, but the error is there before and after

        1. corrupt.content
          322 kB
        2. javaErr1.PNG
          javaErr1.PNG
          22 kB
        3. javaErr2.PNG
          javaErr2.PNG
          29 kB
        4. markup.txt
          49 kB
        5. repaired.content
          322 kB

            [CONFSERVER-21446] Unresponsive script error when default editor set to Rich Text

            Christian Scharr added a comment - - edited

            I can confirm this error in Firefox 3.6.13 with Confluence 3.4.9
            It seems it occurs when somewhere in the site are

            { or }

            used without there macro functionalities (for example in {code} blocks)

            Christian Scharr added a comment - - edited I can confirm this error in Firefox 3.6.13 with Confluence 3.4.9 It seems it occurs when somewhere in the site are { or } used without there macro functionalities (for example in {code} blocks)

            Patrick Gisbey added a comment -

            Hi Tracy,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to this issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards

            Atlassian Support Team.

            Patrick Gisbey added a comment - Hi Tracy, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to this issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you. Regards Atlassian Support Team.

            Theresa Adams added a comment -

            here are the log files. It should be noted however that when I was trying to edit the page - nothing happened in the log file.

            Theresa Adams added a comment - here are the log files. It should be noted however that when I was trying to edit the page - nothing happened in the log file.

            John Ryan added a comment -

            Hi Tracey,

            The simplest method I found, is to open the page for edit using wiki markup in IE8. (other browsers may work - not tested)
            Copy the contents to you clipboard. (This gets rid of the strange characters)
            Clear the content completely, and replace it what's in your clipboard. - Then save.

            I did a revert to an older version, before pasting back, but I don't think that's necessary.

            Cheers
            John

            John Ryan added a comment - Hi Tracey, The simplest method I found, is to open the page for edit using wiki markup in IE8. (other browsers may work - not tested) Copy the contents to you clipboard. (This gets rid of the strange characters) Clear the content completely, and replace it what's in your clipboard. - Then save. I did a revert to an older version, before pasting back, but I don't think that's necessary. Cheers John

            Theresa Adams added a comment -

            How was this handled. We are having the exact same issue.

            Theresa Adams added a comment - How was this handled. We are having the exact same issue.

            Vincent Choy (Inactive) added a comment -

            Jessica,

            Could you please raise a support ticket at http://support.atlassian.com so we can confirm your environment and configuration files.

            Thank you.

            Regards

            Vincent

            Vincent Choy (Inactive) added a comment - Jessica, Could you please raise a support ticket at http://support.atlassian.com so we can confirm your environment and configuration files. Thank you. Regards Vincent

            jessgramp added a comment -

            A user of our Confluence Wiki has also had this problem using Firefox on a Mac and we have tracked it down to the page containing special characters (maybe control characters?). These are valid UTF-8 characters. We are not sure if it's a Confluence or browser issue.

            jessgramp added a comment - A user of our Confluence Wiki has also had this problem using Firefox on a Mac and we have tracked it down to the page containing special characters (maybe control characters?). These are valid UTF-8 characters. We are not sure if it's a Confluence or browser issue.

            Patrick Gisbey added a comment - - edited

            Hi Steve,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to this issue. Unfortunately we cannot provide details of other customers Support tickets as I'm sure you understand there would be security implications. I can however advise that the original ticket for John has not yet been resolved However when resolved the resolution will be posted here for the benefit of other users like yourself who experience the same issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards

            Atlassian Support Team.

            Patrick Gisbey added a comment - - edited Hi Steve, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to this issue. Unfortunately we cannot provide details of other customers Support tickets as I'm sure you understand there would be security implications. I can however advise that the original ticket for John has not yet been resolved However when resolved the resolution will be posted here for the benefit of other users like yourself who experience the same issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you. Regards Atlassian Support Team.

            Deleted Account (Inactive) added a comment - - edited

            What was the resolution here? We have the same issue on certain pages.

            We are also on 3.4

            Deleted Account (Inactive) added a comment - - edited What was the resolution here? We have the same issue on certain pages. We are also on 3.4

            Patrick Gisbey added a comment -

            Hi John,

            I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket.

            Please refer to the support ticket for any future correspondence relating to this issue.

            In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com, not in http://jira.atlassian.com. As our support engineers respond to cases in https://support.atlassian.com, it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you.

            Regards

            Atlassian Support Team.

            Patrick Gisbey added a comment - Hi John, I have created a JIRA support ticket for you at: support.atlassian.com You should receive an email shortly containing a direct link to the support ticket. Please refer to the support ticket for any future correspondence relating to this issue. In future can you please raise support requests such as this by creating an issue in our support system, https://support.atlassian.com , not in http://jira.atlassian.com . As our support engineers respond to cases in https://support.atlassian.com , it will ensure that your problem gets addressed as quickly as possible. Also, https://support.atlassian.com is configured so that only Atlassian and you have access to the case, therefore it is a more appropriate location for us to gather any required system data and configuration from you. Regards Atlassian Support Team.

            John Ryan added a comment -

            I did a test on my backup Wiki, by editing the page in IE8. I reverted to an older version, then copied the wiki markup in from our production wiki.
            I then queried the content directly in the database.
            The 2 files attached are from the production database(corrupt.content), and the backup database (repaired.content)
            If you do a diff on the files, you'll see      Â's. My guess is, they are the problem.

            John Ryan added a comment - I did a test on my backup Wiki, by editing the page in IE8. I reverted to an older version, then copied the wiki markup in from our production wiki. I then queried the content directly in the database. The 2 files attached are from the production database(corrupt.content), and the backup database (repaired.content) If you do a diff on the files, you'll see      Â's. My guess is, they are the problem.

              pgisbey Patrick Gisbey
              4a86cc74bb29 John Ryan
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: