• 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.

Permission problems with Mambo/Jumla installations

M

MaRiOs

Guest
the clients who try to install mambo or joomla by themselves (not by the application pool) they have great problems cause some of the folder containing modules templates and other, have owner and group apache...so the users who install them cant work with them.

Why is that happening? is that normal?
 
This is because the php upload is started as user apache.

A workaround could be to upload the zipfiles (modules, components, etc.) through the Filemanager in the customer menu (Plesk) and use the "Install from directory" option. This way the permissions should stay correct.

Does anyone know how the Filemanager in Plesk takes care of the file ownership?
 
In the Mambo/Joomla administration GUI. When you are at the Component/Module install page you have the ability to

"install from file" --> browse...
"install from directory" --> /usr/local/psa/home/vhost/customer/......
 
Back
Top