# No downloaded modules are loading into Slicer

**URL:** <https://discourse.slicer.org/t/no-downloaded-modules-are-loading-into-slicer/22457>\
**Category:** Development\
**Created:** [March 11, 2022, 4:32pm UTC](https://discourse.slicer.org/t/no-downloaded-modules-are-loading-into-slicer/22457 "2022-03-11T16:32:48Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![tbillah](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/tbillah/32/4139_2.png) [@tbillah](https://discourse.slicer.org/u/tbillah)\
**Post date:** [January 16, 2024, 11:07pm UTC](https://discourse.slicer.org/t/no-downloaded-modules-are-loading-into-slicer/22457/12 "2024-01-16T23:07:52Z")

</div>

Steven, I worked out this solution with Slicer developers a few years back. Would this be helpful to you?

> [@Installing extensions in binary distribution of Slicer](https://discourse.slicer.org/t/installing-extensions-in-binary-distribution-of-slicer/7511/2):
>
> Assuming the user where Slicer and the extensions are installed is called slicer, the idea is to create a script called SlicerWithExtensions.sh along side the Slicer launcher in your shared installation. The script only need to be updated with the name of the user under which Slicer is installed on the cluster: #!/bin/bash -e # This is the username associated with the Slicer installation to share between users. slicer\_user=jcfr # TODO: Update this line script\_dir=$(cd $(dirname $0) || exit …

---

_[View the full topic](https://discourse.slicer.org/t/no-downloaded-modules-are-loading-into-slicer/22457)._