I've refactored most of the source-code of this module(s):

- "core" KT module (kt)
- Shared Login module (kt_sharedlogin) with the xmlrpc logic
- Embedding module (kt_embeddingsite) with the IFrame logic
- REST API module (kt_api) as latest 2.x branch (unchanged)
- CCK Field module (kt_docreference) as latest 2.x branch (unchanged)

Please review the code, waiting for Alex news before committing... new module structure can break active 2.x sites... I think we could still commit the code: a 2.x "official" release have never been published!

Let me know

CommentFileSizeAuthor
#3 kt_1.png43.86 KBthepanz
#3 kt_2.png28.82 KBthepanz
kt.zip36.6 KBthepanz

Comments

alexpott’s picture

I'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...

thepanz’s picture

Yes, 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.

thepanz’s picture

StatusFileSize
new28.82 KB
new43.86 KB

I'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)