Client CSS requires revert in 3.10 STABLE

[NC Software]

It is impractical and unrealistic to expect us to revert our CSS. Instead, how about telling us what the changes are so we can just add/modify them in our CSS. Companies like SoftAir do a lot of CSS modifications and it's horrendous to think of people redoing their CSS.

Also, on the same note, if there are new settings, such as the public/private in the Ticket Statuses, tell us what new areas are in the Admin that we need to investigate.

I'd really like to see a detailed change log other than the inadequate one on builds.kayako.net. I need to see "added public/private modifier to ticket status in Admin" etc.

Lastly, I'm surprised that there is no information e-mailed to customers OR posted in this forum announcing the new stable release.

[Jamie Edwards]

Hi Neal,

I personally think that a good job has been done in keeping reverts required to a minimum.

However, you can easily modify your CSS by saving a copy of your "Old" CSS, revert the template and then compare the two versions either by hand or (more practically) using a comparison software such as http://www.grigsoft.com/wincmp3.htm (or there are freeware versions available out there).

If my memory serves me correctly, the only CSS changed made between the prior stable and this stable is the removal of a "." before the "body" CSS element, but I could be wrong on this. (http://builds.kayako.net/).

[Trevor]

I agree with Jamie,

I would prefer that i had to revert the css some times then to have it not change at all which means it isn’t developing.

I don’t think it has been posted as kayako are just making sure there isn’t any final bugs before telling everyone to update to the new stable.

[NC Software]

I don’t think it has been posted as kayako are just making sure there isn’t any final bugs before telling everyone to update to the new stable.

It's a release! Now is not the time to test it!

As to the CSS, yes, I did use Araxis merge, and when you have a site as heavily modified as mine, it's quite painful to try and figure out what has changed. I think the two lines at the bottom are new (.swift...) and I didn't have .tborder.

Give me a freakin change log people!

[Trevor]

Originally Posted by NC Software

It's a release! Now is not the time to test it!

Why not test it to be 100% sure there isnt any bugs or problems that have been caused by the different code edits?

Originally Posted by NC Software

Give me a freakin change log people!

I dont see any problems with the changelog at http://builds.kayako.net/ Its clear to see what has been changed by reading it.

[NC Software]

I dont see any problems with the changelog at http://builds.kayako.net/ Its clear to see what has been changed by reading it.

Okay, let's take a little test then:

1) Tell me where in the list is there a new property in the Ticket Status for public/private configuration?

2) Where does it specify there was ANY change to the CSS?

3) Where does it state the change (and exactly what page) that the user can now change the STATUS and PRIORITY of their ticket

[Jamie Edwards]

Hi Neal,

Originally Posted by NC Software

1) Tell me where in the list is there a new property in the Ticket Status for public/private configuration?

13 Dec 2006 02:41 PM - http://builds.kayako.net/

2) Where does it specify there was ANY change to the CSS?

http://builds.kayako.net/ - 28 Feb 2007 08:43 PM is one of them.

3) Where does it state the change (and exactly what page) that the user can now change the STATUS and PRIORITY of their ticket

http://blog.kayako.net/archives/59
27 Dec 2006 05:54 PM - http://builds.kayako.net/



Hope the information was useful.

[Trevor]

Originally Posted by NC Software

Okay, let's take a little test then:

1) Tell me where in the list is there a new property in the Ticket Status for public/private configuration?

2) Where does it specify there was ANY change to the CSS?

3) Where does it state the change (and exactly what page) that the user can now change the STATUS and PRIORITY of their ticket

1) Added Public/Private Status Option for eventual ability for clients to change status via Support Center

2) Fixed minor issue with Body tag in CSS

I dont have time to search for these put theres 2, im sure you will find them

[AllureHost]

I try not to edit the CSS too much because I knew that would happen without a doubt, so it was no suprise to me. I simply just added:

media="screen"

To the end of the CSS call in the header template for the SupportSuite CSS and put my sites CSS underneath it so that it uses my stylesheet as a primary and theirs only if the CSS attribute doesn't exist in mine. Saved a bit of time.

[supportskins]

Originally Posted by AllureHost

I try not to edit the CSS too much because I knew that would happen without a doubt, so it was no suprise to me. I simply just added:

media="screen"

To the end of the CSS call in the header template for the SupportSuite CSS and put my sites CSS underneath it so that it uses my stylesheet as a primary and theirs only if the CSS attribute doesn't exist in mine. Saved a bit of time.

I completely agree to this. We use the same method for all our skins.