Vote is now closed. According the result, support for both PHP 4.4 and PHP 5.2 will be dropped in next PhpSwitcher plugin version.
Posts by Nuxwin
-
-
Good morning,
Sorry for late answer. You can find the instructions below but note that I'll not provide any support for such manual changes if you do something wrong.
Edit the /var/www/imscp/gui/plugins/PhpSwitcher/backend/PhpSwitcher.pm file and replace the following lines:
926
by
948
by
Once done, create the /etc/imscp/listeners.d/10_php_keep_packages.pl file with the following content:
Display MorePerl- package Listener::Php::Keep::Packages;
- # i-MSCP PhpSwitcher plugin
- #
- # @author Laurent Declercq <l.declercq@nuxwin.com>
- # @copyright (C) 2014-2018 Laurent Declercq <l.declercq@nuxwin.com>
- # @license i-MSCP License <https://www.i-mscp.net/license-agreement.html>
- # This listener act as a filter to prevent removal of PHP packages that were
- # installed manually.
- use strict;
- use warnings;
- use iMSCP::EventManager;
- iMSCP::EventManager->getInstance()->register( 'beforeUninstallPackages', sub {
- @{ $_[0] } = grep ( !/^php[\d.-]+/, @{ $_[0] } );
- 0;
- } );
- 1;
- __END__
Then, look at the following howto to setup additional PHP versions from Ondřej Surý repository: https://gist.github.com/nuxwin…0ad81680521db5e445587af22
Bear in mind that in the current PhpSwitcher plugin version (4.0.3) a psw<version>-fpm service will be created, even for Ondřej Surý PHP versions. So, basically, you SHOULD disable the default php<version>-fpm service that is provided by the package. The current version of the plugin will only act on the psw<version>-fpm service. Assuming systemd as init system, you can disable the default provided service as follows:
You need to do that only for additional PHP versions, that is, those setup for the PhpSwitcher plugin. Don't do that for the default PHP version which you selected through i-MSCP installer. In the coming PhpSwitcher version (5.0.0), the plugin will make use of the default service as provided by the package as it will be able to differentiate self-compiled versions of packaged versions.
Regarding Ondřej Surý packaged PHP versions: You need manage these versions as usually. PHP extensions need to be installed through APT and can be enabled/disabled using the php(en|dis)mod tool. If you do so, don't forget to restart the psw<version>-fpm service once after.
-
As long as you don't drop 5.3 and up, I'm ok... but my whole reason for purchasing phpSwitcher was for a client who needed 5.3 for his app.
One day, he's going to have to do a (painful) upgrade, but for now, its not in the cards.
We are talking about PHP 4.4, 5.2 here...
-
I would go further and drop anything older than 5.6 - 5.4 is already a critical security problem and should not be supported anymore, 5.6 is officially old and outdated before the year is out - even supporting that will provide problems to the server provider, the customer and other users of the internet (hacked CMS sending spam any many more scenarios).
I cannot. There are still some ISPs asking me to keep support for PHP 5.3. Anyway hacked CMS most of time has nothing to do with the PHP version in use. Bugs are generally in the CMS itself. Note that for PHP versions 5.3 up to 5.6, I'm still backporting security fixes when needed.
-
Dear community,
Support for both PHP 4.4 and PHP 5.2 versions has been provided since the first version of the PhpSwitcher plugin, even through those versions were already not longer supported by upstream PHP team.
As time goes on, it become really hard for us to support these versions that are not longer compatible with various development libraries provided by newest OS versions. Also, these versions don't provide the PHP FastCGI process Manager (fpm) and so, they are not usable with the i-MSCP apache2/fpm server implementation which should be your first choice.
As a reminder:
- PHP 4.4 is EOL since 7 August 2008 (~ 10 years ago)
- PHP 5.2 is EOL since 6 January 2011 (~ 8 years ago)
We think that it's time to drop support for these "prehistorical" versions as nobody should rely on them. However because we care about our customers, we open this poll to let's you choose.
Thank for your participation.
-
Dear community,
A new version of the DomainAutoApproval plugin has just been released:
Version compatible with i-MSCP Serie 1.3.x, 1.4.x and 1.5.x
CHANGELOG
- Fixed: Fatal error: Call to undefined function client_mail_add_default_accounts() - iMSCP 1.5.x
- Renamed: 'user_accounts' parameter to 'client_accounts'
- Renamed: 'ignored_domain' parameter to 'ignored_domain_aliases'
Thank you for using our plugins.
-
Good evening,
Please don't use the github branch. You need install the last released version, that is, the version 1.5.3: https://github.com/i-MSCP/imscp/releases/tag/1.5.3
Then, you need follow the following steps: https://github.com/i-MSCP/imsc…n/INSTALL.md#installation
-
-
I'll release the plugin in few hours. I've finally updated all patches for self-compiled versions and also added support for PHP 7.2, 7.3... To resume, with next version, you'll be able to:
If you use the Fcgid i-MSCP server implementation (not recommended):
- Setup PHP 4.4, 5.2, 5.3, 5.4, 5.5, 5.6, 7.0, 7.1, 7.2, 7.3 (self-compiled versions)
- Setup PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.x ... (packaged PHP versions)
If you use the FPM i-MSCP server implementation (recommended):
- Setup PHP 5.3, 5.4, 5.5, 5.6, 7.0, 7.1, 7.2, 7.3 (self-compiled versions)
- Setup PHP 5.6, 7.0, 7.1, 7.2, 7.3, 7.x ... (packaged PHP versions)
And of course, in both cases, I recommend usage of packaged versions over self-compiled versions...
Sorry for the delay.
-
Could you provide me with the path to the file?
/var/log/mail.log