Posted on: 2008/5/4 21:35
Re: Would XOOPS be able to do all this?
In general, by default most contents in XOOPS are handled per group instead of per user.
Thus you need write your own module(s).
Pico can manage permissions by user.
It is also quite easy to run a clone of the module,
a category or a simple page by group or by user.
You can also import content from one document
to another but also from a clone to another (get it by id)
Define a stylesheet/theme by clone, by category or by page.
Within XOOPS Cube
you can extend it with 'Preloads'
And smarty plugins with both XOOPS and Legacy ^^
And finally, personalize your language catalog, wrap content, vote, diff, views/download, and even create html forms that are managed through the control panel, sent by email, etc.
D3 modules have two more advantages - interoperability and security - you can manage 'Comments' with D3Forum, which also means 'content reusable' and easily create a discussion around a topic/presentation, whatever... You benefit from the secure concept of XOOPS_TRUST_PATH (originally suggested by XOOPS Cube
programmer Minahito) and implemented by Gijoe (ref. Protector)
D3 modules should work fine with the last xoops.org release
If not, it should be a priority task of the core team.
Have Fun !
I like people more than machines or money. But that's me!
Lets do something good and great: Lets do open source!