As of Version SixCMS 6.0.6patch2 this Bug is fixed. The patch can be downloaded 
from our support site.

Reply via email to