Closed (fixed)
Project:
ELMS: Course Information System
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2013 at 06:16 UTC
Updated:
20 Jul 2013 at 12:07 UTC
Jump to comment: Most recent file
Comments
Comment #1
btopro commentedpiece them all together, it's just lots of contrib mashed together in differentw ays. these are intentionally being fragmented to create something different then the LMSs of yesteryear that will be outdated the day they are implemented.
Comment #2
kaizerking commentedthere are lot of conflicts when we do so,
especially the roles and permissions
Comment #3
kaizerking commentedhere is the features screen shot showing the conflicts
Comment #4
btopro commentedYes sorry, I was refering to having to piece it together on your own if you wanted to use it in that way.
THis is intended to be implemented like follows:
distro.domain
so that each distribution is deployed as a subdomain of the same primary domain. For example in our setup I'm deploying the following way:
CIS - online . collegename
ICOR - interact . collegename
MOOC - courses . collegename
CLE - studio . collegename
Then the automation scripts included in CIS are used to automatically generate multi-site instances on each of the other distribution homes. This will provide an ultimately longer term, sustainable learning network without the need to stick to 1 version of Drupal 5 or 10 years from now. This is not a stand it up and play with it immediately kind of environment (yet) but I'm always trying to nudge it there.
Comment #5
btopro commented