>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3545047. --> Reported by: [pameeela](https://www.drupal.org/user/1431110) Related to !616 !606 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Testing Drupal CMS on Hostarmada, I was able to get around the timeout using the workaround in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3511967" title="Status: Active">#3511967: Package Manager tasks can exceed wait_timeout on cheap hosting</a></span>, but got another error trying to add a module:<br> <code>SandboxEventException: The new package drupal/drupal_cms_content_type_base will be installed in the directory /recipes/drupal_cms_content_type_base, which already exists but is not managed by Composer. The new package drupal/drupal_cms_google_analytics will be installed in the directory /recipes/drupal_cms_google_analytics, which already exists but is not managed by Composer. The new package drupal/drupal_cms_image will be installed in the directory /recipes/drupal_cms_image, which already exists but is not managed by Composer. The new package drupal/drupal_cms_page will be installed in the directory /recipes/drupal_cms_page, which already exists but is not managed by Composer. The new package drupal/drupal_cms_privacy_basic will be installed in the directory /recipes/drupal_cms_privacy_basic, which already exists but is not managed by Composer.</code></p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Try to use Project Browser to install a module on Hostarmada.</p> <p>Installed version of Drupal CMS is 1.2.2 as that's what Softaculous offers currently.</p> <h4 id="proposed-resolution">Proposed resolution</h4> <p>See #8 for the cause of the problem reported above. The fix is to obsolete drupal_cms_analytics. That's already done; we just need to roll a new release to reflect it.</p> <p>The database timeout issue will be fixed in core, but we can work around it in this issue.</p> > Related issue: [Issue #3541137](https://www.drupal.org/node/3541137) > Related issue: [Issue #3545576](https://www.drupal.org/node/3545576)