2 results found

1. Post-update hooks in WordPress Toolkit

   Add post-update hooks in WordPress Toolkit, which can be used to automate the process of committing to Git (e.g. WordPress core and plugin updates that are automatically installed by WordPress Toolkit).

   Use case:

   Be able to respond to the event and write a program to do things like: a) commit the changes to the local git repository and push them to origin, b) trigger an alert in the monitoring system

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   This feature will be available in WPT v6.7

2. remove/update the app options (wikis, CMS, bulletin boards, Squirrelmail etc)

   These are so out of date as to be seriously vulnerable, with versions that mostly cannot be readily installed without installing PHP version 7.0 and (often) to add in the mysql module to PHP even if you are using that.

   These options should be removed unless it can be upgraded to the latest versions of PHP and the mysql module added to PHP - at the very least something on the page BEFORE installation saying that this will require outdated and unsupported versions of PHP and any additional modules so people

   a) know the dangers and also
   b) so they do not have to go through the steps of installation only to find that they do not have those things installed and will have to do that.

   ideally, too, if they have a warning, but want to go ahead:

   1) it would be good to have in that warning something to actually install the deprecated versions of this software automatically as part of that process and
   2) where appropriate, to offer installation to a subdomain if there is a risk of overwriting an installation that exists where the user is going to install it.

   At the moment, you can do a custom install but that is not necessarily obvious on the install page as 'custom' requires the dropdown and there is no warning before Laravel or Afterlogic overwrite your, e.g. Wordpress install, whilst the Nextcloud and Mattermost ones will not do an overwrite but install alongside.

   These are so out of date as to be seriously vulnerable, with versions that mostly cannot be readily installed without installing PHP version 7.0 and (often) to add in the mysql module to PHP even if you are using that.

   These options should be removed unless it can be upgraded to the latest versions of PHP and the mysql module added to PHP - at the very least something on the page BEFORE installation saying that this will require outdated and unsupported versions of PHP and any additional modules so people

   a) know the dangers and also
   b) so they… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Web Applications  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input and consideration for keeping Plesk and its users safe. We are aware that the catalogue is currently outdated. The APS technology itself is outdated. Plesk is currently in the process of replacing the old catalog system with a new extension.

   -- SH