Ok...now that we've said all that, we need to be able to reproduce the issue from the ground up, if we're going to fix an issue.  There are a number of different settings, dnn permissions, event config parameters. 

I'm starting to think that there are too many agendas on this module and that we need to simplify....Not only that, but folks that don't understand how DNN works are making statements like "simpler task to add RSS to the module "....RSS already exists and works in the module!!!  We have tested this.  So I think there are a number of issues going on besides "the module does not work".

Also, we need to be realistic in a scenario  for instance: "The secondary (homepage) module is set to List as the only view and the site owner does not have edit rights for this module"....  Let me ask, we would "Site Owner" not have permissions to a module?  This is a real concern...Site Owners are the Site "God"...this scenario does not work for me.  So already we are into an unrealistic scenario...

Anyhow, thanks for the info.

I don't want to get in a disagreement...but can you please define "Content Creator".  Who can add a new module to a page?  Last time I looked, only a "Site Admin" can add new modules to a page.  Are you referring to the "event creator"?  The term "Content Creator" does not exist in any DNN documentation or the Event Module.

The way the module was intended to work is that:
1) Admin always has full rights, including module settings, events, etc.
2) Moderator Role (if enabled) has full rights to all events
3) Module "Edit" Users only have rights to the events they create
4) View User roles work as expected and can see any module events

You cannot expect a linked module (ex. List Module instance pointing to a another Event module Instance, using the subcalendar feature) to override the original module authorization.

If these are not the "use cases" expected, please define specifically, the use cases (all of them) for use permissions on the module.  This is the only way we can be assured that we all agree w/your use cases.

Oh and one more point I need to clarify, because there seems to be some misunderstanding about this in many instances where users provide feedback about modules.

Point: I am not providing you with a list of things I want fixed. What I am providing is feedback detailing issues with the use of the module in a given scenario. As the project leader, you are the person who has to take it all in and determine what the module will do and how it will do it. It's entirely up to you.

However, without a strategy document or a specified purpose, all that one can go by is what the module settings imply and allow. My scenario falls well within the settings of this module and the DNN framework and also directly arose from functionality of the previous version of the Events module.

I'm really not fussed whether you decide to fix things I bring up or not, but I stand by each and every issue raised.

That's my bit said 

Rob