I created a module and put it on a page that All Users can read.  If I'm logged in as Host it works great.  If I don't login, I can see the module but none of the buttons, DDLs do anything.  They're not greyed out, the just don't work.  If I set a breakpoint in the Event Handlers of these controls and run the debugger, it never hits the breakpoint.  I wrote another module and it works fine for all users, but I don't see why one works and the other doesn't. 

Is this a common "gotcha" for newbie module develpers?

I"m not sure what the cache implications are.  I have cleared cache from Host:Settings:Performance Settings link.

I have "Module Caching Method" set to Memory

Performance Settings set to "Moderate Caching"

Authenticated Cacheability set to "ServverAndNoCache"

Is there something else I should do?

And I discovered that I don't have another module that works.  It only worked becuase I had that pages permissions set so All Users could Edit.  Once I removed that, none of the buttons on that page worked.  so it seems my whole site is this way.  I am running Medium Trust.

I'm making progress.  If I create a new module by using the DotNetNuke Module Template, my buttons do not work unless the user has Edit permission on the page.

But, if I just create a Web Control (.ascx file), and install it by hand instead of using a manifest file, everything works fine. 

What does the template do to modify permissions that doesn't get done when creating/installing by hand?