In the past when we've dropped modules from the distribution, we've created issues for sites that used modules that depended on the module that was dropped. That was a problem for both References (dropped in favor of Entity Reference) and Response Image (dropped in favor or Breakpoint).

I've already added a message on the Crew Connect project page, but we should take this opportunity to add the structure for warnings about modules that need to be moved to sites/all if a site wants to continue using that functionality.

We have a pretty good structure for warnings from the work done on #2113223: Show warning if no media_[provider] modules are enabled and the code to figure out if a module is in the profile or sites/all is in https://drupal.org/project/profile_status_check.

Comments

coderdan’s picture

Status: Active » Needs work
StatusFileSize
new2.26 KB

I didn't use the profile switcher logic to determine the location of the module, so maybe you will want to modify that. But I took a stab at it anyway. Will need to modify the .make file to include this patch.

coderdan’s picture

Here is the patch for the make files within the profile.

libkuman’s picture

I just tested the patch to om_crew_connect.install on MNN and it worked as expected for the following cases:

1. Initial State of the module turned off, applying patch prevents it from being turned on
2. Initial State of the module turned on, applying patch makes a warning appear on /admin/reports/status
3. Moved module to sites/all/contrib-cm, different warning appears on on /admin/reports/status

kreynen’s picture

I've rolled a new beta4 release of Crew Connect. The version needs to be updated in the .make files for all 3 distributions. We should continue including Crew Connect in beta5 (and possibly beta6), then drop it in any releases after that.

libkuman’s picture

Assigned: Unassigned » kreynen

assigning to kreynen so that he can add this to all 3 starter kits

kreynen’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.