Did I miss it? Was the plugin released?
Wow, that's very good news, I'll definitely wait!
Thanks a lot for your work!
Hey Nuxwin ,
I'd really prefer to wait for an official upgrade path. I read your recent posts on Twitter regarding PHP7.x tests are now passing. Really appreciate your hard work on this.
Could you give a rough schedule for the release maybe? I'm currently facing resellers who will leave if they woun't get access to PHP 7.3 soon.
I know, it's hard to tell, but should I expect it more like two weeks or two months until the next release?
I'm already too new. Should I just downgrade?
Downgrading would result in removal of a whole bunch of packages:Quote
~ # apt-get install libssl1.1=1.1.0k-1~deb9u1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libarchive-zip-perl libexttextcat-2.0-0 libexttextcat-data libfastlz libfile-listing-perl libfile-stripnondeterminism-perl
libhtml-tree-perl libhttp-cookies-perl libhttp-negotiate-perl libicu57 libjansson4 libjs-jquery libjs-sphinxdoc
libjs-underscore liblzo2-2 libmail-sendmail-perl libnet-http-perl libpython3.5 libsctp-dev libsctp1 libstemmer0d
libsys-hostname-long-perl libtcl8.6 libwww-robotrules-perl libyaml-0-2 po-debconf postfix-sqlite python-backports-abc
python-cffi-backend python-chardet python-concurrent.futures python-croniter python-crypto python-cryptography
python-dateutil python-enum34 python-idna python-ipaddress python-jinja2 python-markupsafe python-msgpack python-openssl
python-pkg-resources python-psutil python-pyasn1 python-setuptools python-singledispatch python-six python-systemd
python-tz python-urllib3 python-yaml python-zmq python3-pycurl python3-urllib3 ruby-did-you-mean ruby-minitest
ruby-net-telnet ruby-power-assert ruby-test-unit sqlite3 uuid-dev vim-runtime
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
apache2-dev apt-listbugs bareos-common bareos-filedaemon ca-certificates dovecot-core dovecot-imapd dovecot-mysql
dovecot-pop3d liblwp-protocol-https-perl libruby2.3 libssl-dev libwww-perl libxml-parser-perl openssl postfix
python-pip-whl python-requests python-tornado python-virtualenv python3-debianbts python3-httplib2 python3-pysimplesoap
python3-reportbug python3-requests python3-virtualenv rake reportbug ruby ruby-debian ruby-domain-name ruby-gettext
ruby-http-cookie ruby-httpclient ruby-locale ruby-soap4r ruby-sqlite3 ruby-text ruby-unf ruby-unf-ext ruby-unicode
ruby-xmlparser ruby2.3 rubygems-integration salt-common salt-minion ssl-cert vim-nox virtualenv
The following packages will be DOWNGRADED:
0 upgraded, 0 newly installed, 1 downgraded, 49 to remove and 0 not upgraded.
I also started to implement the mentioned solution to be able to install php7.3 - hopefully in a non-intrusive way to allow future i-MSCP and PhpSwitcher upgrades without problems.
Currently I'm stuck with this error:Quote
The following packages have unmet dependencies:
libssl-dev : Depends: libssl1.1 (= 1.1.0k-1~deb9u1) but 1.1.1c-1+0~20190710.13+debian9~1.gbp359e02 is to be installed
[ERROR] main: An unexpected error occurred: An error occurred while installing build dependencies: E: Unable to correct problems, you have held broken packages.
I'm already running 1.1.1c-1, which was pulled in from packages.sury.org
Did I already do a mistake previously? Do I need to pin 1.1.0k-1? Will this result in any other issues?
Thanks for any advice.
I'm also waiting for support of newer PHP versions. Please be aware that PHP 7.1 is no longer actively developed since Dec 1, 2018, and security update support ends on Dec 1st 2019.
I really try not to do manual modifications like mentioned in the previous post - that's why I bought the plugin - to prevent issues that might occur when updating the plugin later. Could you please upgrade the plugin to be able to use at least PHP 7.2, or could you please confirm that no issues will arise when following the steps in the previous post and upgrading the plugin later on.
I see, thank you for clarification.
Be aware that because the phpinfo files are static, you must re-generate them each time you made a configuration change for a specific PHP version (e.g. when you enable or disable a PHP/Pecl extension). This task can be done through the PhpSwitcher administration interface.
I did re-generate the files using the WebUI, so I thought that this will be enough to show the correct values.
we have some customers for which we still need to provide php 5.6, and I realized shortly, that the information shown in the i-MSCP WebUI (Domains -> PHP Switcher -> Show phpinfo) differs from what is shown in the php.ini configuration file, as well as a manually executed phpinfo().
In /opt/phpswitcher/20180301/php5.6/etc/php-fpm.d/subdomain.domain.tld I have the following settings (all set using the WebUI). I manually removed phpinfo from the disabled functions to be able to compare phpinfo output.
After changing the disabled_functions value, I restarted psw5.6-fpm.service.
When I open the phpinfo in the WebUI (Domains -> PHP Switcher -> Show phpinfo) it shows a post_max_size = 8M and upload_max_filesize = 2M (see Screenshot 1), while an info.php in the Webroot shows 96M as expected (Screenshot 2).
Is there a misunderstanding from my side?
I'm running the latest release of i-MSCP (1.5.3 (2018120800)) on Debian 9.7 with PhpSwitcher Plugin Version 4.0.3 (Build 2017111000). PHP-FPM is in use.
Ooops, there is a plugin version 3.5.0, which solves exactly this issue, renewing 21 days before expiry.
I'm sorry! Problem solved.