Hello,
Last time, I was changing the colour of the Design by “Look and Feel”. But suddently the webpage has changed and most of my changes get losen. After that I tried to get the oroginal colour I selected last time, but nothing has changed. I although tried to change the source code, but nothing happens. No reaction. I thought that the Oxid System has a default and is not reading the source Codes from its File on the Server. Why did this happen? 
You 're right! Thats why i advice my customers not to use the Look&Feel-Tool. It sets the whole CSS-Code to the default values with the new colors. So if you don’t have a backup, there is no other way but doing your changes again.
And remember: [B]Don’t use the Look&Feel![/B]
@JKrug - what’s the alternative ? The 860 line oxid.css is well structured but its still a big task to go through and manually edit all the fields from scratch. As fas as I know, there are no other WYSIWYG tools for OXID css or smarty to help this process - or am I wrong ?
I still find the look&feel tools useful to get a first impression of how to implement a new customer colour scheme. The process I use is to first create a custom theme, and then to use the look&feel tool to try out colour combination in this new custom theme. Once I reach the limit of what can be done with the look&feel tool, I use Firebug and Dreamweaver (or Eclipse) to do the rest of the job. Of course, once you start to manually edit oxid.css, you can never go back to the look&feel tool for that theme.
Perhaps someone has a suggestion for a better work process ?
CPJ
[QUOTE=cpjolly;31830]Once I reach the limit of what can be done with the look&feel tool, I use Firebug and Dreamweaver (or Eclipse) to do the rest of the job. Of course, once you start to manually edit oxid.css, you can never go back to the look&feel tool for that theme.
Perhaps someone has a suggestion for a better work process ?
CPJ[/QUOTE]
That is the only way to work with look and feel. Additionally, you can work with a demo / test shop. There you can try out new color or whatever with look and feel, then you can use a compare tool to bring the changes to your original oxid.css.
That is an easy way to work with look & feel when you have already done manual changes to you oxid.css. You just have to stick to make changes manually.
CYA
[QUOTE=cpjolly;31830]@JKrug - what’s the alternative ? The 860 line oxid.css is well structured but its still a big task to go through and manually edit all the fields from scratch. As fas as I know, there are no other WYSIWYG tools for OXID css or smarty to help this process - or am I wrong ?
I still find the look&feel tools useful to get a first impression of how to implement a new customer colour scheme. The process I use is to first create a custom theme, and then to use the look&feel tool to try out colour combination in this new custom theme. Once I reach the limit of what can be done with the look&feel tool, I use Firebug and Dreamweaver (or Eclipse) to do the rest of the job. Of course, once you start to manually edit oxid.css, you can never go back to the look&feel tool for that theme.
Perhaps someone has a suggestion for a better work process ?
CPJ[/QUOTE]
I feel much more comfortable when editing the css-File by hand. Changing the colors with search and replace its faster then doing it with the L&F-tool.
But a solution can be, that you don’t do changes in the oxid.css by hand so you can always use the tool. Instead you do your manual changes in a separate CSS-File and include that one after the oxid.css. So your manual css-changes will not be overwritten by L&F.