I was looking at the unzipped installation, and the drupal 3rd party files are not in the sites/modules/ folder.

/profiles/uberdrupal/ maybe there is some performance reason or is it an updating thing or something?

I'm OK with it, just thought I'd ask the reasoning behind it.

I'm wondering why that is. Afterall, aren't additional 3rd party modules installed into the sites/modules/ folder?

Comments

narcissus921’s picture

narcissus921 commented

I've wondered this too, though the only thing I can come up with is conflicting modules from other profiles/packages. My current UD install has everything ripped out of the profile and into the sites/all/modules/* folders for easier updating - conflicts if the module is in the profile and you forget it's there and put one in sites/all/modules. Plus a multi-profile configuration runs into the aforementioned problem of conflicting modules. Ugh.

Subscribing.

rszrama’s picture

rszrama commented
Status: Active » Fixed

It's really just a feature of the automatic packaging script here on d.o. You can move them to sites/all/* prior to installation if you want to - it won't cause any problems.

rszrama’s picture

rszrama commented
Status: Fixed » Closed (works as designed)
narcissus921’s picture

narcissus921 commented

Thanks for clearing that up, Ryan. I had always been curious about that, and any implications it may have.

What about moving post-installation? Say I want to expose those modules to a multisite config, would that cause any problems?

rszrama’s picture

rszrama commented

It's technically possible, because Drupal knows how to re-index its system table to find the proper filepath if a module suddenly doesn't exist where it was expected. I'm not entirely sure of the process, so do it on a test site first, but I typically just moved modules around and then resubmitted the modules form to relocate them.