Yes this has been a problem since day one. DNN doesn't allow one to create a good workable page editor role. It basically makes someone with edit rights on a page an administrator of the page and all sub-pages when all that one really needs in that role is the ability to insert and delete modules. That function needs to be separated from the full page editing permissions.

In addition, this situation has given rise to the issue that many modules are inconsistent in the way they expose editing functionality. Some developers assume that everyone working on a site will be an administrator and their modules present all editing options only within the module settings menu; which is only accessible by the page editor role. Other developers more usefully place content editing rights on their own menu item and make it visible to roles specified within the module settings.

For example, I have a bunch of Datasprings modules that are not usable by my clients unless I give them full page editing rights. This sort of thing can make a module useless and it really should not get past the DNN review program.

Rob

P.s. I also think they should tell developers to stop using a single DNN-Reviewed graphic to make it look as if all their modules have been reviewed.