Recent content by TomP

I actually tried that once and it didn't work. I tried it twice with the same results, but maybe I did something wrong. I don't know what it could have been though because the directions are pretty straight forward.

That is the problem. There doesn't seem to be an easy way to set the "shell" version. Most of my systems that run at the command prompt level. like Drush, and Composer, all warn that they will no longer work soon unless PHP shows at least 8.X . The trick I did as I said above does seem to be...

All the sites are set separately to run the latest PHP. When I was logging in SSH as one of the site admins or even root, it was always showing 7.4.

I think I solved it, but I'm not sure if this will keep working. When I run 'which php' I get: /usr/bin/php so I followed it. /usr/bin/php is a symlink to /etc/alternatives/php. /etc/alternatives/php is in turn a symlink to /usr/bin/php7.4, which is the php file for version 7.4. I went to...

I am using Plesk ver 18.0.48. Ubuntu 20.04.5 LTS. All the sites are set to run PHP 8.1.12 through their subscription on Plesk. When I run '/opt/plesk/php/8.1/bin/php -v' I get this: # /opt/plesk/php/8.1/bin/php -v PHP 8.1.13 (cli) (built: Nov 28 2022 06:40:38) (NTS) Copyright (c) The PHP Group...

Sorry I can't do much right now because I'm on just my phone till tomorrow. I'm using Ubuntu on the server updated to the latest through Plesk updates. I'll check more in the morning. Thanks

Now I've removed the .bash_profile since things seem to be getting worse. when I run drush updatedb I get this: [warning] Your PHP installation is too old. Drupal requires at least PHP /8.0/. It is recommended to upgrade to PHP version /8.0/ or higher for the best ongoing support. See PHP's...

Thank you. I gave it a try by creating a .bash_profile file in the site's root directory: export PATH=/opt/plesk/php/8.1/bin:$PATH alias composer='/opt/plesk/php/8.1/bin/php /usr/lib64/plesk-9.0/composer.phar' cd siteroot 'siteroot' being the actual root of my Drupal site. I logged out and back...

I've had a similar problem to this before. Apache on my Ubuntu server running Plesk is still using PHP 7.4.3 (cli). The Drupal sites are using 8.1.12. When I try to install some of the modules that require 8.1 or greater are not installing using composer because the module is seeing the 7.4.3...

It sounds like I used the wrong one. I'm not too worried about resource usage, but being notified when the server goes down is a big help. I am concerned about security because I've had a few hacks done on a couple of Wordpress sites I had to clean up.

I have Plesk 360 installed, but I've been wondering if I should switch to Imunify360? I know they both do different things, but Imunify360 looks like it does so much more. Has anyone had experience with it? Does it cause any problems on a Linux (Ubuntu) server?

I realize that, but if Plesk would ship with CentOS 8 that would fix it all.

That's kind of what I thought after researching this. This is all such a pain because of the new requirements of the latest Drupal. I know the apache 2.4.6 has all the backports added to it, so why doesn't CentOS and Plesk update the version to something newer.

I've been reading dozens of posts about the versions of Apache running on Plesk. I have a server running Plesk Obsidian Version 18.0.29 Update #3, and CentOS Linux 7.8.2003. I am looking into upgrading all my Drupal sites to the latest version, but one of the requirements is Apache 2.4.7, and...

I asked this problem in a drush forum. One of the suggestions was to change one of he lines in .bashrc to: export DRUSH_PHP='/opt/plesk/php/7.3/bin/php' Same results though. Script keeps failing.