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

Colour Scheme Setting for 'Top Bar' is not working after browser cache flush or opening Confluence on private/incognito browser window.

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 8.4.0, 7.19.9
    • None

      Issue Summary

      This is reproducible on Data Center: (yes) 

      Steps to Reproduce

      1. Login to Confluence->General Administration
      2. Colour Scheme 
      3. Click on Edit and change 'Top Bar' colour to any other colour and Save
      4. Now, open a new browser window in Private/incognito mode and paste Confluence Login URL. 
        Or, flush browser cache and open Confluence login page.

      Expected Results

      Top Bar in Login page should display the selected colour for Top Bar in Colour Schema Setting page.

      Actual Results

      Top Bar in Login page displaying default Blue colour in login page.

      Workaround

      1. Login to Confluence->General Administration > Colour Scheme
      2. Click on Edit and change Top Bar to different colour and set it back to previous colour.
      3. Save
      4. Now, re-login to Confluence and you will see required colour.
      But the only caveat is if you open Confluence URL in Private window/Incognito mode then it will show you the Blue colour in the login screen. Basically, as long as users are not flushing the browser cache and opening the Confluence URL in private window/Incognito mode, the login screen will display the Top Bar colour as it is set in the Colour Scheme page.

            [CONFSERVER-90659] Colour Scheme Setting for 'Top Bar' is not working after browser cache flush or opening Confluence on private/incognito browser window.

            There are no comments yet on this issue.

              Unassigned Unassigned
              76633c495724 Jai Shori
              Affected customers:
              2 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: