Module Naming
- The module names need to be seriously reviewed for clarity and alpha order
- For example Monitoring, Service Items, PortalSearch (they would expect that under plain search) are just not connected to what the modules do.
- Link and LinksEnhanced are in correct AlphaOrder - EnhancedLinks ends up with the E's not L's.
- Blacklist should become UserBlackList for example.
- Also quite a few of the module names are just obscure/inscrutable for someone to know what they are inserting - and renaming is needed.
(I am happy to do this - rename all modules)
Weather Module
The Weather Module that appeared in latest build required registration. Very frustrating for newbies inserting it. Never have modules that require registration in a core build. When I taught last weeks class I had room full of angry and confused people when attempting to insert a simple module I didn't have on the non registered one.
http://www.xmethods.com
has a ton of non registration based WS that could have been used.
If you accidentally slip with your mouse and select 1 country in the
settings dialog (Armenia for example) then everyone who goes to site is from Armenia and cannot choose a country. The limiting of a site to 1 country is not a feature that should be activated accidentally.
FireFox is not being correctly identified in any of the monitoring / Logs module.
I think a checkbox should allow hiding of admin Modules. Ultimately in future build Roles should determine what modules they see but for now a checkbox for Admin would make the list so much smaller and easy for user to browse.
The SignInCool is hardely that - either give them something cool or ditch it. Don't over-pomise and under-deliver.
The idea of a LogOut link and SignIn link, etc. should not be separate modules. We just need a "linkmaker" module that has a dropdown for all things they may want to link to.