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

'JavaScript served in header' option disables Link Browser and Autocomplete

XMLWordPrintable

      If the 'JavaScript served in header' option is set to Off in the General Configuration, autocomplete does not work and anything to do with the Links Browser breaks (the Insert Link button does not load in the WYSIWYG editor and the Insert > Link, Insert > Attachment and the Insert Attachment buttons do nothing).

      Furthermore, the sidebar for the General Configuration screen recommends to set the 'JavaScript served in header' option to Off to increase page load performance. It warns that it might disable some plugins, but doesn't mention which ones or that autocomplete/the Links Browser will be affected.

            [CONFSERVER-19220] 'JavaScript served in header' option disables Link Browser and Autocomplete

            Michael S added a comment -

            Option was removed in 5.0. Closing as obsolete.

            Michael S added a comment - Option was removed in 5.0. Closing as obsolete.

            Bob Swift added a comment -

            More specifically, keep the option in property file or similar, but take it off the screen so someone has to go out of their way to set this.

            Bob Swift added a comment - More specifically, keep the option in property file or similar, but take it off the screen so someone has to go out of their way to set this.

            Dennis Kromhout van der Meer (Inactive) added a comment -

            In my humble opinion, we're growing towards products where client side code such as javascript becomes an absolute requirement for the product to fully function, which means that disabling javascript in (corporate) environments is getting less.

            Valuable comment from https://answers.atlassian.com/questions/42750/javascript-served-in-header-affects-on-plugins:

            So, I think you are saying that Administrators should never turn OFF serving javascript in the header since it will break many things in base Confluence as well as various plugins. Perhaps the referenced item should discuss a fix that removes the option from the Confluence admin screen to make it more difficult for administrators to shoot themselves in the foot?

            Dennis Kromhout van der Meer (Inactive) added a comment - In my humble opinion, we're growing towards products where client side code such as javascript becomes an absolute requirement for the product to fully function, which means that disabling javascript in (corporate) environments is getting less. Valuable comment from https://answers.atlassian.com/questions/42750/javascript-served-in-header-affects-on-plugins: So, I think you are saying that Administrators should never turn OFF serving javascript in the header since it will break many things in base Confluence as well as various plugins. Perhaps the referenced item should discuss a fix that removes the option from the Confluence admin screen to make it more difficult for administrators to shoot themselves in the foot?

              Unassigned Unassigned
              akdominguez Katrina Walser (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: