In DNN, if a module uses a Postback to itself, must you set the Cache timeout to zero? What I'm seeing is if the timeout is not zero, the cached Html fragment is displayed and the control tree is not rebuilt on the server, so your postback event cannot be processed. What I mean is if you put an <asp:linkbutton> or similar in your module's default view, for that to work propelry you have to set the cache timeout to zero.

Is this correct or am I mixed up? If I'm not mixed up, why did it take me so long to notice this?

Wouldn't this core functionality work better if in PortalModuleBase the method CreateChildControls only used the cached Html fragment if the request was NOT a Postback? That simple test would let you set a non-zero cache timeout that would only affect the Display of the module on its first request, but not on postbacks.

FYI, the code I'm looking at is DNN 3.2.2, so this may have changed in later releases.