Installation for D7 fails

D6 is the stable branch, D7 is a starting point, the leads me to believe that context_var needs some patches to comply with OG. it's very hard to hit a moving target with OG being in active 2.x branch development but patches most welcome.

I had the same issue.

The errors listed were preceded by notifications that I was missing modules Spacer_theme, htmlpurifier (and it's download library) and workflow_purl - none were included in the distribution. Downloading them and increasing available memory in my settings.php file allowed the installation to "complete" but I see only a single drupal homepage with a single link "add new content" that links to "book page" Manually linking the admin url allows me to view the module list which shows nothing but chaos tools activated, so it would appear that the installation did not complete, it terminated. If there was any way to know which modules to activate to continue I would persist, however I'm guessing that the database is likely missing entries available only through the install, and not through just the module activation process anyway. I would like to evaluate your distribution once it is working under drupal 7. Thanks.
-equinox-

7.x is in development, please jump in and submit patches where possible. We'll get to D7 a lot faster with community input. As for evaluation please see the 6.x version as it's heavily tested and very stable.

added spaces_theme, workflow_purl, and htmlpurifier to the download routine so at least those missing projects should be included as of tonight's build

The installation also failed for me so I looked in the apache error logs and found:
Call to undefined function content_filter_xss() in /profiles/elms/modules/contrib/context_var/plugins/context_var_context_condition.inc on line 70
Changing content_filter_xss to filter_xss fixed that problem but then I got:
Call to undefined function og_get_group_context() in /profiles/elms/modules/contrib/html_export/html_export_og/html_export_og.module on line 19
so I did a global replace of og_get_group_context() with og_context()

The install then finished with the previously mentioned warnings and then added these notices

Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).
    Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).
    Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).
    Notice: Undefined index: og_user_roles in features_install_modules() (line 553 of /profiles/elms/modules/contrib/features/features.module).
    Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).
    Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).
    Notice: Undefined index: base in view->fix_missing_relationships() (line 579 of /profiles/elms/modules/contrib/views/includes/view.inc).

I'm not sure what to do about the og_user_roles issue, and haven't looked at the other undefined index at all. I've attached a patch file for what I did (patch -p1 from installation root).

The patch I submitted failed testing because it dealt with the context_var module, the html_export module and the requirement_dashboard module. Also FYI, og_is_group_admin($group) needs to be replaced with og_user_access($group,'administer group'). That appears in a bunch of other files.

Thank you for the patch, made sense to me why it failed; I believe I've committed those changes in those modules previous but I'll have to check again; tough switching gears from D6 to D7 the way I have while stil building out D6 actively but I'll see what I can do :). Also thank you for the og_user_access translation, I was having issues finding the conversion for that function. Any opinion on OG 1.x vs OG 2.x in 7?

patches applied to other projects and additional og clean up for admin checking also applied. Try out the next dev build tonight to see if it's fixed.

Thanks that helps a lot / kind of confirms my suspicions. Have heard that 2.x is shaping up to be great, as this project is still early going in D7 I'll jump on 2.x early so we're not stuck with a difficult migration down the road.

Wanted to take a shot at todays version of 7.x-1.x-dev but the download links are 404-ing. Any hints on where to look for the "og_user_roles" undefined index issue and the "base" undefined index issue?

hmmm,og user roles has been dropped from d6, where is the notice again. not sure of base. also try in the morning you may just have clicked before it was built since dev releases are lower priority for the packaging script. maybe a patch to drop the og user roles issue entirely is needed.

transferring data to new CPU tomorrow, then will start into correct feature migration of all content types

Thanks, I'll play around with 6 until the links are working for 7 for me

Looks like 7x packaging script failed last night (d.o. issue) ;\. I pushed some minor changes in a commit so it'll be live tomorrow hopefully. 6.x dev is stable and has added functionality of bookmarking, quizzing, and webform integration.

packaging error resolved; must have been a hiccup

Didn't have time to investigate much, but got this error installing the D7 branch:

Fatal error: Call to undefined function og_get_group() in /var/www/html/elms7x/profiles/elms/modules/contrib/spaces/spaces_og/plugins/space_og.inc on line 15

Not sure why it's saying that's an undefined function, it looks good to me. Maybe a syntax error? here's the line:

$this->og = og_get_group('node', $this->id);

Any idea what the replacement is then? Just loading the node and reading $node->gid?

Will need a proper patch at some point in spaces_og_clone but I can give $node->og_group_ref['und'][0]['target_id'] a try

I noticed in the installation that ELMS User Management is dependent on OG_User_Roles. Upon investigating OG_User_Roles, does not appear that it is going to be upgraded to 7.x, how is that going to be addressed when the install requires it?

FYI: I received these errors on completion of the standard ELMS 7.x install:

Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /home/school/public_html/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined variable: replacements in uuid_tokens() (line 95 of /home/school/public_html/profiles/elms/modules/contrib/uuid/uuid.tokens.inc).
Notice: Undefined variable: replacements in uuid_tokens() (line 95 of /home/school/public_html/profiles/elms/modules/contrib/uuid/uuid.tokens.inc).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /home/school/public_html/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /home/school/public_html/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: references in features_install_modules() (line 553 of /home/school/public_html/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: og_user_roles in features_install_modules() (line 553 of /home/school/public_html/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: references in features_install_modules() (line 553 of /home/school/public_html/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: og_user_roles in features_install_modules() (line 553 of /home/school/public_html/profiles/elms/modules/contrib/features/features.module).

The references and go_user_roles I can understand, because those modules are not included in the distribution-but am not sure about the errors for theme and uuid.

I also continue to get when I go to the Modules page:
Notice: Array to string conversion in ctools_get_plugins() (line 253 of /home/school/public_html/profiles/elms/modules/contrib/ctools/includes/plugins.inc).

Looks like it will need to be dropped from the installer. the features package was machine ported and not fully built out. We'll get there though a lot of elms user management may be invalid because of advancements in OG. Taking the requirement out of that file will help with installation as it's been dropped from 6.x anyway. Patches always welcome. Also Spaces theme and Spaces OG Clone need some love in 7.x as current roadblockers.

I'm not quite good enough to write patches yet. Still working on writing my first module. Just wondered if you could tell me how to remove the og_user_role dependency. I've spent a couple hours reading the code and would like to learn how that's done.

Anyway, I also found that if you update the spaces module through the module update page, it will crash the entire system and the only way to restore is to reload the profile directory. I've tested it twice to verify that what caused it. Other modules seem to upgrade just fine.

I was hoping to start out with the 7.x version, rather than building an entire site in 6.x and then trying to upgrade later on, but maybe will not be able to. It would seem that it would not be a simple upgrade if the user subsystem is completely written differently between the versions of Drupal.

Removing dependency is as easy as going to the .info file of the module and disabling.

If you want to start out in D7 and build out from there you might want to take a look at Ulmus as this is where development for ELMS will stabilize before ELMS does in D7. The install routine also works there (I think).

6.x is in development still as we are using it and a lot of the code from it in other courses / systems. There's a lot of really positive conversations and commitments in the community right now and so we're starting to see how these all play out going forward. OG has stabilized a lot in the last few months and that was one of the major roadblocks to any D7 system like this.

ckeditor link OG removed from packaging list, also entire .info file and .make files rebuilt to mirror Ulmus at the moment. Things will continue to change as Ulmus develops and conversations surrounding it evolve but please feel free to keep the feedback coming.

I've got more of this kind of errors in a clean install:

Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: profile2 in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: references in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: views_fluid_grid in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: views_slideshow in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: workflow in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: og_user_roles in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: profile2 in features_install_modules() (line 553 of /var/www/elms/profiles/elms/modules/contrib/features/features.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).
Notice: Undefined index: theme in elms_site_menu_alter() (line 47 of /var/www/elms/profiles/elms/modules/elms_features/elms_site/elms_site.module).

These are all notices which will not cause issues on install, you can disable the notices in PHP by changing the error_reporting value.

It is also important to note that elms_sites will / the elms_features package is just there in a semi-ported state. ELMS is currently intended to be used in Drupal 6 and will first defer to the features of Ulmus and that will have elms_sites / elms_parents under a different name space as ulmus_sites and ulmus_parent.

Noticed the dev version was removed from the project page.

Is there still momentum to bring this up to a full D7 release?

Please see Blockers for Drupal 7 in the g.d.o. discussion thread. Currently I have my time spit between 4 other distributions so I'm trying to work on general projects that benefit the myriad of distributions I work on, ELMS included. The majority of this overlapping effort is currently being put into the MOOC distribution (listed as Drupal as Course on g.d.o. thread). The major difference between the ELMS distro and MOOC is that ELMS is effectively MOOC but with the added complexity of OG thrown in so I'm trying to get all the things that don't rely on OG ironed out before proceeding forward with anything for D7. Removed the dev from the home-page cause it's not in any shape to be used at this time.

Six months later... what's the status with using ELMS on Drupal 7? If Drupal 8 releases as announced this August, D6 will no longer be supported by drupal.org at that point. I'm very interested in getting ELMS up and running, but I'd rather not have to go through a painful upgrade from D6 to D7 in 3 months if I can avoid it.

I can't seem to figure out how to get ELMS working with D7 at this point, though. The three different distributions described on the main ELMS page don't seem to come with any documentation (and don't seem to include all the required packages). I've been trying to manually track down and add all the appropriate packages, but og_user_roles and a few other listed requirements aren't available. CCK_Redirection has been renamed Redirection for D7, and while it will install, it wants the "Content" project, which no longer exists under that name. Meanwhile, ELMS Content still expects the old name.

emdalton. There is no real working version of D7 "ELMS" as a stand alone distribution which is why there is code set towards a Dev branch but no release / nightly build available on the project page. If you are looking for a download it and solve all your problems solution that's Drupal based you currently aren't going to find it. Open Atrium hasn't migrated to a full D7 version yet and as a lot of the work in this original distribution is based on that, there's nothing to follow suit on. I am 1 developer tackling 6+ distributions, they are a dedicated company (P2) that hasn't yet upgraded one of their most successful platform builds.

The project page is as it stands, this has been split out into multiple setups as it is being structured for a new type of enterprise level learning network as opposed to 1 system that can be stood up in 1 place. My context is such that I need to setup something enterprise grade and the D6 version of ELMS was much more a small scale, point and get a mini-learning-management-system of sorts (obviously with pieces missing).

There are currently no plans to extend this name space in D7 as it is an umbrella term now though it is not abandoned. D6 ELMS stacks exist and will need ported at some point, higher education / gov always trails behind in adoption so I wouldn't expect that to occur until D8 has been out awhile. There's also been lots of talk of a D6 maintainer being paid by the Drupal community to maintain security releases so it's not really being sunsetted. It is the Windows XP of Drupal and will be around a very, very long time.

Thanks for the explanation. I hope D6 does continue to be supported-- a lot of what I need for various projects isn't ready for D7 yet.

I don't mind putting together a system of my own from modules-- I don't need (or even particularly want) a "complete" distribution that claims to solve every LMS need, since that would probably be harder to customize for my specific project.

That said, I find the notes on the various ELMS-related pages confusing. It isn't really clear that all the D7 distros are incomplete works in progress, nor how they are supposed to work together when they are complete. While I certainly appreciate your "one developer shop" situation, it's possible that a short remark on each of the ELMS project pages to the effect that D7 is not yet complete would save users like myself a lot of time, and result in fewer questions directed to you. :)

yeah probably should just build your own out of contrib. ELMS is a nice picture of what's possible but at the end of the day we all need to maintain these things long term so kinda pointless waiting on someone else to write what you'll ultimately have to maintain when it comes to key functionality of a system. Bug fixing is one thing but if you need something to workflow a certain way, you'll have to dig into code anyway.