Issue Joomla Toolkit - autoinstall...

[ChristophRo]

Server operating system version

Debian 1x

Plesk version and microupdate number

18.0.75

Looks like you guys forced an auto installation of the Joomla Toolkit extension with it's latest 3.0.10 release on all servers....I do not like that!

But what's even more annoying, is the fact that it's not possible to uninstall it anymore without encountering an error, that may or may not leave stuff behind.
This then that may or may not break our servers in the future...who knows, but it just feels terribad

 

[Sebahat.hadzhi]

Hi, @ChristophRo . The installation was performed due to the upcoming APS Catalog deprecation. Joomla! Toolkit is being installed on servers with Joomla! websites to preserve the ability to manage Joomla! instances through the Plesk interface. I will consult further with our team about the issue you are reporting and try to gather more details on whether there are leftover files. Thank you in advance for your patience in the meantime.

 

[ChristophRo]

OK, I see now the incentive on why you force an automatic installation.
But as the Joomla Toolkit is a paid extension and to my knowledge not usable at all without a subscription...I still don't agree with that move. (well, I do in general never agree on any automatic Extension installation, except maybe on fresh server installs....)

 

[Sebahat.hadzhi]

Thank you for the update. Joomla Toolkit's free version still provides basic functionality. Hence, covering the absence of basic functionality of the APSC.

There's an option to disable automatic extensions installation by adding to panel.ini the following lines:

[ext-catalog]
extensionAutoInstall = false

 

[Sebahat.hadzhi]

@ChristophRo , I want to clarify that the information I provided in my last reply is incorrect and apologize for misleading you. The snippet is effective for controlling if extensions can be automatically installed in case the license for the same is present on the server. It does not prevent rollouts of core Plesk extensions. Thus, in this particular case it won't have the desired effect.

The only way for is to completely block the extension according to the following guide:

• https://support.plesk.com/hc/en-us/...hide-extensions-from-Plesk-Extensions-Catalog