5: Re: Custom themes (response to 4)
Posted by Voice Admin on

Hmm, maybe it was a cache thing - the css file either in your browser cache or in our cache (we run a cache in front of the Voice servers to make things faster under high load).

Is it a reprodudible problem for you? (or anyone else?) where changing the custom css doesn't straight away have any effect?



6: Re: Custom themes (response to 5)
Posted by SOFRA on

It happens about 3 out of 5 times.  Now I know that this happens, I know to wait a bit to see the results of a change to the custom .css file.