Strauss Maximus wrote
I have used MyPHPNuke and Xoops thus can only talk about those.
MPN was a phpnuke fork. However the upside of it was it was not module based. the forums, gallery, news etc areas were all hardcoded in. Thus it was a all inclusive package. While you may not have had the variety you do with say DNN or Xoops you knew at the very least everything worked and there were no core code vs module incompatibilities. It was one simple d/l and boom done. That was a nice feature from a simplicity & efficient standpoint. However I do not hold it against DNN because the devs also maintain core modules so this really isn't a issue for the most part it seems.
Been awhile since I used MPN but from what I recall; the down side of MPN was the lack of WYSIWYG editor. Thats self explaining I am sure. Also the admin panel was a spaghetti mess of panels and controls within panels and controls. Was VERY non-intuitive and non-friendly jumble. Also the block controls were fairly basic. However it did have a HUGE amount of themes many of them were excellent and well done. Sadly the dev team about a yr or so ago went though some bleeding and the project last I saw was more or less on life support at best. Very little work being done on it and the support forums are almost silent.
As far as Xoops, in the over 2 yrs I used it did add many modern features such as MS word type editor and very slick/clean admin panel. However the dev team was its own worse enemy. They 'reversed' the code path. when I got on board they were working on the 2.0.x ver of the core. they then moved too the 2.2 path which included a huge amount of additions and changes that most modules needed to be updated for to work properly. They then during this time dropped support of dev team supported modules and left all module development to 3rd parities, then a little less then a yr ago they decided the 2.2 code base wasn't going in a direction they wanted so reverted and stated the 2.0.x code base was now, once again, the official version. This needless to say caused a LARGE amount of chaos in the months that followed. As most modules failed to work with the older code. And since the dev team no longer supported official modules and more... you get the idea. The situation has since stabilized but for those of us still on the 2.2 code base (going backwards and loose many features we are now dependent on was not a option) we were left up a creek w/o a paddle. As all the updates modules now are more and more failing to work with the old(new) official core. This is why I decided to jump ship and how I came across DNN.
Thanks for that insight.. feels good to be on greener grass :)
Strauss Maximus wrote
Some features from those above CMS's I'd actually like to see:
1. a quote and insert image button on the default GUI editor that comes with DNN. (I for some reason see the editor on this site different the the editor that came with my install, as it has a insert image button)
The current distribution includes FTB editor, while dotnetnuke.com already uses FCK editor. We have plans to make FCK editor the default editor in new distributions. If you want to use FCK Editor yourself now, just go to the downloads page, and download the FCK editor provider package. Mind you, it cannot be installed like a module, so please follow the install notes included in the package
Strauss Maximus wrote
2. A easier/cleaner way to edit/add/remove the graphic emoticons on the forums.
3. A top x posters and a listing of the last x newest posts block in the forum module
There will be a new forums module soon (currently in beta), with tons of new features. BTW, i find myself using the smileys that come with FCK editor (just like on this site), instead of the smileys provided by the forums module
Strauss Maximus wrote
4. A module to have site visitors view the registered users list/info that is searchable/sortable by various criteria
Tony Valenti is working on that module, it will be called Membership Directory
Strauss Maximus wrote
5. Enable submissions by non-admins on all core modules
Edit rights on modules are set on a per module or per page level to roles you defined yourself.... Wouldn't that cover your need?