• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

cms within httpdocs?

A

admin123

Guest
Can someone tell me whether a cms can be installed in httpdocs directly? Whenever i use plesk to install cms, it puts it within its own folder. so, i tried to install myself manually in httpdocs and I get the : Warning: open_basedir restriction in effect. File is in wrong directory.

But I do have safe mode off, so why doesn't it let me install there?

thanks.
 
Issue Resolved...

CMS doesn't like to be moved i guess so i installed fresh copy manually and it worked.

thanks
 
True, most packages do not like to be 'moved' manually after they have been installed.

You can install a package into the root httpdocs folder (usually not recommended), but not currently through the Plesk control panel (there is another thread which discusses their reasoning). This can be accomplished either by manually installing the rpm, or using something like 4PSA's Integrator (their version of App Vault).

As to the open_basedir error, this is common for many packages (osCommerce, various CMS's, etc), and can be resolved by putting directives into either the .htaccess, vhost.conf, or http.include files. (this topic has been covered numerous times in other threads).

This is not a Plesk 'bug' or 'error', there is no way to have a server pre-configured for all possible scenarios. Locking down the open_basedir is actually a good security measure, then only allowing it for specific domains which have a valid reason for needing it; rather than opening it up server wide.
 
Back
Top