Maybe I should clarify this question. You (Catzwolf) talked about implementing core features into all modules through and through... do you mean the core features from the upcoming 2.1 or do you mean fully implementing all the core features already available in 2.05 through all the current core modules.

Hey Catzwolf, would it be possible for you (or anyone) to provide a pretty good explanation of what the possibilities are for the current core modules?

Not having digged through the code myself I'd like to know what is possible with what's already available... to sum up with a question: Do the current modules fully utilize the capabilities already available or do they barely expose the potential and if they are somewhere in between, are they closer to one or the other?

Big Core request:

Permissions.

I'd like to see everything treated as an object with permissions in a child parent tree. Each forum post, download, article, news item... not just categories or sections. Permissions should also be inheritable so that child objects get the parents permissions but can be modified to include more or less permission for groups or users. Child objects can be moved to new parents and inherit their permissions as well.

Each object includes a way to link to it's settings, ie: it is referrable via url from a page or from admin section. For instance, when you list all articles there is a link next to each that will give you a permissions edit page. Also on each article page there is a link for same (viewable only by admin). Each type of object should have a list capability in admin. This would be for editing as well as admin functions. A toggle for showing group(/user) access rights as well so you can audit the objects without having to click each one. Alternatively, admining a group should show a list of objects they have access to.

Users/Groups:

All Users are virtual Groups. Treat them both the same except that Users have a flag set that they only have one member. Groups can have limited number of members. Groups can include Groups, which is necessary for Users to be treated as Groups. Groups have child parent relationships with other Groups, ie: Anonymous is parent to all, Registered is child of Anonymous and Admin is Child of Registered... all other Groups are children of Registered. Group permissions are inherited, So when I create a new Group under Registered I don't have to assign anything old, just new stuff.

Anonymous - Login, Read General News, Read Articles A, B, D, Read Forums A, C
.....|
.....Registered - Same as above plus: Submit General News, Read/Comment Articles C, E, F, Read/Post Forums A, B, C, D
..........|
..........New Section View Group - Same as above plus: View/Submit Section News, Read Articles G, H, I, Read Forums E, F
...............|
...............New Section Editor - Same as above plus: Edit Section News, Edit Articles G, H, I, Edit Forums E, F
....................|
....................New Section Admin - Same as above plus: Admin Section News, Admin Articles G, H, I, Admin Forums E, F
..........|
..........Another Section View Group - etc.

..........|
..........Admin - Admin all and Users, Groups


Of course modules should be able to use these new hooks, encouraged to use them....

I just realized that you can go to the modules admin page and update the module templates.... so this could solve the other person's problem if it was related to modules...

Is this related to updating a module template? I've found that when you install a module it compiles it's templates into the database... one time only. This is a very unfriendly behavior for anyone who wants to re-theme a module or modify it's layout, especially after having entered lots of new content...

any comments on this from developers? Are there any plans to implement proper Smarty themes for modules?