External apps install modules to sites/all/modules which creates a problem when I want to update modules I've previously added.

There's no easy way to know which modules I previously installed and which are part of apps.

Change to install apps to a separate apps directory. Then at least I can check to see if a module was installed from an app and shouldn't be updated independently.

This brings up another point - if I previously had installed a module that's part of an app that I subsequently install but isn't the same rev level, what happens?

Seems the only present way to be sure is to check and see what modules are included in apps before installing but that information isn't readily available.

Better yet make the apps engine smart enough to recognize a possible conflict and flag the app installation.

It would also be nice if the module updates report had some flags to indicate a module's origin, i.e. if it's part of an app. I'm guessing that means a change to Drupal core. Maybe something the Module Filter module could handle.

Comments

JKingsnorth’s picture

Project: Open Atrium » Apps
Version: 7.x-2.26 » 7.x-1.x-dev

This issue might be better raised in the 'Apps' project, since Open Atrium just uses this framework. I'll move this issue over to that project.

druplicate’s picture

This is a default configuration issue.

The Apps module can be configured to install in any folder - it's currently defaulted to /sites/all/modules.

You can change this yourself before you install any external apps in fact, but the default should be something else, like /sites/all/modules/apps. This is in fact how it's set up for apps that ship with Open Atrium:

/profiles/openatrium/modules/apps
/profiles/openatrium/modules/contrib
/profiles/openatrium/modules/panopoly