> I think I found the problem myself. I just checked the 'compress js > and css' in the configuration. From there it was not a problem > anymore. How could that happen? Is the there a difference in the code > interpretation while compressed or not? If you added custom JS code (which how looks like you did) and did not produce 100% tidy code the compression may break your code. I suggest to use jslint [1] to see what may wrong about your code. Most probably it's ommitting needed semicolons. Andi [1] http://www.jslint.com/