Imagine creating a distro that supports two different types of sites: a blog style site and a news style site. Now imagine that you create a custom commenting module for this distro that is appropriate for both. Where should this module live? It can live in sites/all, but best practices say this should live in the profiles/my_profile/modules folder since you want the module to remain pristine and only be updated during a profile update. Right now, because there are two profile folders in my example, you need to have two copies of the custom commenting module or you need to create a shared folder somewhere and symlink to it.
Niether is ideal.
UPDATE: it turns out that if you use a symlink and put modules in some other location, that their simpletests will not run. This patch solves that issue as well...
Simply by adding one line to drupal_system_listing() function this can be accomplished.
Needs discussion, review, & documentation
Closed: duplicate
9.5
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Brought this up in #yes-no-queue in slack. And @catch brought up
think this can probably be marked duplicate of recipes. The custom commenting module would be a recipe probably.
So going to do that but if not the same please reopen updating issue summary with how this is unique.
Thanks!