• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Installing Drupal modules go into wrong directory

TomP

Basic Pleskian
I'm testing out how well Plesk does with installing Drupal, and I thought it looked like it would be a breeze. That is until I tried to log into my installed site, and add a new module. I found that the new module was installed into the drupal default modules directory, not the /sites/all/modules like I wanted.
Is this a problem due to the Plesk install, or am I missing something in my Drupal setup I have never needed to know before?
 
It's gotta be a Drupal thing, because Plesk is not interfering with internal website configuration at all.
 
Back
Top