Hi, It's always recommended to apply hotfix in development environment and check it was applied correctly and to catch any potential issues after hotfixing. This case would be such example (although rare). Regards, Zdenek

Hello, This was a bug in the 5.5 version of kentico (hotfix 18). the problem should disappear by applying the hotfix number 20 for the version 5.5. I am sorry for the inconvenience. Best regards, Boris Pocatko

Hi, Regrettably, this is already known bug that appears after applying hotfix 5.5.23. I'm very sorry for this inconvenience. Could you please apply the latest hotfix (http://devnet.kentico.com/Bugtracker/Hotfixes.aspx)? Best regards, Michal Legen

Hi, could you please apply the latest hotfix for 5.5 version? Unfortunately, there was a bug and nested macros were not resolved correctly. I am sorry for inconvenience. With the hotfix below macro will work. {(1)%sitecontext.currentuser.userid|(equals){(2)%currentuser.use...

Hi, Please download the latest hotfix for 4.1 version which is 4.1.21 from this page - . Instructions are included in the hotfix package. Best regards, Juraj Ondrus

Hello, There has been a bug which could cause such a behavior in Kentico. Could you please try to upgrade to 5.5R2 if you haven't already and apply the latest hotfix (this issue sould be fixed in 5.5R2 hotfix number 4)? Best regards, Boris Pocatko

Hi, actually I am replacing the aspx and cs files within the folders. Does it mean that you did not copy the content of bin directory? To apply the hotfix successfully .dll files have to be replaced as well. Best regards, Ivana Tomanickova

Hi, We are sorry for this inconvenience. However, this bug was already fixed in the latest hotfix for 5.5 version - devnet.kentico.com/Bugtracker/Hotfixes.aspx. Could you please download and apply the hotfix? Best regards, Miro Remias.

I downloaded the hotfix and it does indeed work. I had looked through the hotifxes the other day but had missed this one. I'm not sure why it would be a licensing issue to do the transformation in the control directly, but the hotfix does work, though it's not ideal to have ...

I tested this again after applying the latest hotfix and it's back to working as it should. I don't know if the hotfix is responsible for fixing that problem but it's no longer occurring on our web site. aim