Hi, Thank you for reporting. It is really a bug in the current version. I am sorry for inconvenience. It should be fixed in the next hotfix. Best regards, Ivana Tomanickova

Hello, We don't recommend such an approach. The wizard won't be patched to create a "hotfixed" database. You need to install a copy of Kentico at first together with the database and apply the whole hotfix according to the instructions afterwards. Best regards, Boris Po...

Hi Francis, Thanks for the update. Which version exactly have you used before applying the hotfix? Please let us know if you encounter any further errors. Regards, Zdenek C.

Hi Zdenek, I did not apply any hotfix before, so it is the installer version that possibly contains the bug, The hot fixe applied was the latest one, i think it is 5.5R2.37, I'll verify... Thanks Francis Harvey

Hi, Which version of Kentico CMS do you use? I am using 5.5R2 with latest hotfix and it is working just fine for me - even if the pre-compiled site is not updatable. Best regards, Juraj Ondrus

I just tested the url you indicated is not working in v5.5.4223 and it works fine. It also works in the Denver edition of version 6. Maybe it will work if you apply the hotfix for v5.5.4223

Hello, now that there´s the first hotfix for the 6th version I would like to now the best practice to upgrade the Denver release I´ve been working on for one month to avoid loosing all the work. Thanks for your help in advance

Would it be possible, and simpler, to just apply the hotfix first, then re-run the installer, rather than edit the scripts? Also, safe to presume that the 6.02 exe contains all the fixes from 6.01? (Do I need to download both patches, or just the 6.02?) -Gary

Juraj, That's exactly what I was hoping to hear. It sure would be nice to not have to run the hotfix util against any/all new instances I setup during my eval of Kentico. -Gary

Hello, The problem could be that the update calls the URL of the site, which is the URL of the site defined in KIM. That input is not checked for correctness (e.g. missing protocol etc.). Could you therefore please check the entered URL of your website? Best Regard...