Ticket #456 (new enhancement)

Opened 1 year ago

Last modified 5 months ago

Success messages should not be red

Reported by: pasichnyk Assigned to:
Priority: trivial Milestone: ispCP ω 1.1.0
Component: Frontend (GUI) Version: ispCP ω 1.0.0 - DEV
Severity: Hard Keywords:
Cc:

Description

Usually error messages are red, and success messages are a less alarming color (blue, grey, etc).

Attachments

Change History

07/02/2007 11:00:13 PM changed by raphael

  • type changed from defect to enhancement.
  • milestone changed from ispCP ω 1.0.0 - RC3 to ispCP ω 1.0.0.

07/03/2007 02:35:09 AM changed by raphael

  • priority changed from minor to trivial.
  • milestone changed from ispCP ω 1.0.0 to ispCP ω 1.1.0.

I'm not against this change, but it requires a lot of rewriting and I'm not sure anybody wants to do it for 1.0.

07/03/2007 12:32:43 PM changed by zothos

hm, if the changes are too big. Then put it on the milestone > 1.0. easy :P

09/22/2007 10:06:11 PM changed by pasichnyk

I agree that this could be pushed off to > 1.0 if the changes are too big. I would rather see the system all up and running 100% and red success messages, then a buggy system and blue success messages. :)

It's just "fit and finish" but its alarming when i expect something to succeed and i get a big bold red message. :)

Also i noticed a simiar thing. In lists like "domain aliases", "subdomains', etc... If it doesn't return any rows we get: "Subdomain list is empty!" in bold red. I think these messages should be lighter... in a dark grey maybe... and just state "No subdomains exist..." or something less alarming. After all its not an error, its just a note that there aren't any added.

02/17/2008 02:44:45 PM changed by rats

  • severity set to Hard.
  • milestone changed from ispCP ω 1.1.0 to Working.

02/23/2008 06:15:04 PM changed by rats

  • version changed from ispCP ω 1.0.0 - RC2 to ispCP ω 1.0.0 - DEV.
  • milestone changed from Working to ispCP ω 1.1.0.

Add/Change #456 (Success messages should not be red)