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

Edit disk security feature feedback request

O

OlegB

Guest
We have some requests with report about customers with problems with our new security schema. Sometimes customers need to fix our security manually. But this has one unsolved problem when the next time we are setting our security we will have rewritten customer settings… We understand this problem but want to know customers reaction to our suggestion before. We want to give customers ability add custom settings to our security, so at the next time we will take into account customer custom settings and we will have set correct security for our customera. But we don’t want add customers ability to override security settings strongly required by Plesk, usually this is allow permissions. So customers will have ability to add custom allow permissions, for example to override not required by Plesk our deny settings. We could make some UI to add/edit/import/export customer custom settings.
 
One thing that we see frequently is the need to have a single directory for uploaded content for CMS systems. (Images, etc) And we also frequently see .asp sites that need Access DB's placed just outside the webroot (same level as /httpdocs).

It is pretty important that the CMS systems stay working once the permissions are set on their content folders and especially that the Access directory permissions stay working.

We have no problems if you lock down Plesk specific files/folders, but we do need to be able to allow clients to set some permissions (I am willing to restrict that to just under the httpdocs folder, provided we can setup the access db folders above the httpdocs folders).

I know a lot of sites are moving to SQL Server/SQL Express, but it will be a couple of years before all the old Access based sites are gone, and I don't think we will ever get around the CMS upload issue.
 
Back
Top