Issue Details (XML | Word | Printable)

Key: CONF-6228
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Jens Schumacher [Atlassian]
Votes: 5
Watchers: 3
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

Global custom color scheme is not used by spaces

Created: 23/May/06 02:05 AM   Updated: 20/Jul/06 12:39 AM
Component/s: Web Interface
Affects Version/s: 2.2
Fix Version/s: 2.2.5

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. Untitled-1.jpg
(195 kB)
Issue Links:
Blocker
 
Reference
 

Participants: Carl Harris, Eric Salonen, Jens Schumacher [Atlassian], Kalle Hallivuori, michael k and Tom Davies [Atlassian]
Since last comment: 2 years, 50 weeks ago
Resolution Date: 18/Jul/06 04:13 AM
Labels:


 Description  « Hide
After the upgrade from 2.1.4 to 2.2.1, the global custom color scheme is not being applied to spaces. Visiting the Space Admin tab, the global custom color scheme is available for selection. However, the space custom color scheme is selected by default. In the 2.1.4 and prior versions, the global custom color scheme would be used by a space unless overridden in the Space Admin tab.

The upgrade to 2.2.1 was performed by exporting and restoring to a new instance. The problem affects all existing spaces, as well as newly created spaces.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Eric Salonen added a comment - 22/Jun/06 12:56 AM
We also upgraded from 2.1.4 to 2.2.3 and we are experiencing a similar problem. (We created a new instance and imported data via xml).

Ill try to explain this clearly.

In the "Administrator-> Colour Scheme"-view, we can only modify the "Custom Colour Scheme". There is absolutely no way to modify the "Global colour scheme", which can also be chosen in the individual space admin view. At least the global colour scheme doesnt appear anywhere in the administration-view.

But once we modify the one and only "Custom Colour Scheme" in the administration-view, the colour scheme that gets modified is the "Global Colour scheme" in the individual spaces.

And as Jens reported, for each space the "Custom Colour scheme" is selected by default.

So I guess this is a "bug" or just a "wording"-problem. The name in the administration-view should probably be "Global Colour Scheme" instead of "Custom Colour Scheme".

Ill attach a screenshot of the administration view, so you can see that the only colour scheme is the custom colour scheme.


Eric Salonen added a comment - 22/Jun/06 01:04 AM
Forgot to mention, we would also like the "Global Colour scheme" to be selected by default for each space. We have over 100 spaces and it would be rather annoying to go and select the global colour scheme for each space

michael k added a comment - 27/Jun/06 12:12 AM
We are also experiencing the same problem when upgrading from Confluence 2.1.2 to Confluence 2.2.2 (I have also experienced the same result when upgrading to Confluence 2.2.4) using an external database and Weblogic 8.1. We are using the xml file generated using the built in backup process in 2.1.2 and then restoring Confluence 2.2.2 using the xml file.

Is there a work around for this?

We have had to reconsider upgrading due to this bug.


Carl Harris added a comment - 27/Jun/06 07:57 PM
Since I originally reported this as a support issue, I thought I should mention that my organization also finds this issue to be more than a minor cosmetic nusiance. It is very important to my management that our websites have a common color scheme that fits with the organization's public relations standards. Having to reapply our standard color scheme every time a new space is created (or after a space admin decides to get creative with the color scheme) is becoming a bit of a headache. Please correct this problem.

Jens Schumacher [Atlassian] added a comment - 28/Jun/06 07:12 PM
Carl,

Just letting you know that this bug is on our to do list for the next release.

Cheers,
Jens


Kalle Hallivuori added a comment - 18/Jul/06 07:36 AM
Hi.

We're testing upgrading to 2.2.5 and this feature very much applies to it!

How can I fix coloring of all spaces after upgrade from 2.1.x to 2.2.x? We have a large number of spaces and would like to have some kind of verifiable, automated process for this rather than going through color settings of all spaces one by one.

Is there perhaps something that can be done inside the database or on the command line?

Cheers,

Kalle Hallivuori / Sulake IT Support


Tom Davies [Atlassian] added a comment - 20/Jul/06 12:39 AM
Hi Kalle,

This issue is fixed in 2.2.5. Can you describe exactly what happens in your case?

What should happen is this:

  • set a custom global colour scheme in Administration, Colour Scheme
  • create a new space
  • go to a page in the new space, and the global colour scheme should apply to it.

Does this not work for you in 2.2.5?

Thanks,
Tom