Active
Project:
KnowledgeTree integration
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2010 at 15:59 UTC
Updated:
12 Nov 2010 at 11:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
alexpottI'm not sure about breaking everything up into smaller modules...
On the plus side everything is easier to maintain and sites only enable exactly what they need.
On the minus side there probably will come a time when something gets duplicated... although I guess that would then mean it has to go to the "core" module.
I'm going to review this work over the weekend...
Comment #2
thepanz commentedYes, what I have in mind is to make modules lightweight and simple. The user can enable only what he/she needs.
If a setting (like KT root url, or maybe in the future also the secret-key) needs to be shared across sub-modules that's the right time to move it to the core module.
The .zip file I've attached above is only a "preview", some functionality may not work as excepted.
Comment #3
thepanz commentedI'm currently working on new features for fine-tune the sync between Drupal users and KT ones:
- allow new users into KT
- allow password, username, email update
- allow update of KT user's groups with Drupal's user Roles
- (TODO) allow update of KT user's groups with Drupal's user subscribed Organic Groups
Here two previews of what I've done so far (modules kt_sharedlogin and kt_embeddedsite)