Last post Jan 11, 2006 02:50 PM by jhenning
Dec 30, 2005 11:38 AM|fzshaikh|LINK
Jan 11, 2006 02:50 PM|jhenning|LINK
I know I saw another post on this issue, but for the life of me cannot find it... maybe I am ignorant, but could someone search for the post regarding this and link it to this response?
The problem was introduced with the turning off of viewstate in the visibility control (admin\Containers\Visibility.ascx).
<asp:LinkButton ID="cmdVisibility" Runat="server" CausesValidation="False"
If you enable the viewstate of the cmdVisibility your problem will go away... not sure if this is going to be the "real" fix applied, but it is an acceptable workaround for now.