I also have this exact same problem.

I am using one of the default DNN-Yellow containers (and I've tried the DNN-Yellow).  The only way I can get the edit option to appear for a non-admin user is to set the cache time to 0.

This is occuring for me across several modules.

Again, setting 0 cache time is a workaround, but the editable areas are not high use, so a cache time of up to 1 hour was what I intended to use.

I've also found that if the cache value is set to a non-zero value, even if the caching is turned off completely on the host menu, and the cache cleared, I still see the problem.

Any further thoughts?

Rob

I'm running DNN 3.2.2 on my XP Pro system for development.

I had this same problem but always had the cache set to 0 and changing the container had no effect.  However, I realized that I had moved the database from MSDE to SQLExpress.  I had a backup copy of the MDF file from before my sql upgrade.  I copied that file to a SQL 2000 server and attached it and pointed my dnn install to that server - created a role, created a user, put the user in the role, gave edit rights to the  module to the new role, logged in as the user - and it worked!  Same DNN web site content and modules, same data in the database (except for the new user/role). 

So be cautious about moving the database to Sql 2005/Express if you're still running 3.x.x.  There may be other things in play here but this was my experience.

I had used the attach method to get the database into SqlExpress - didn't get any errors and the dnn site worked fine - except for the permissions.

Toby