Bug: Version 5.0.0 has been released, but it requires PHP 8.x

[dixitalmedia]

Hi all,

Hosting automatically was updated from PHP 7.4.33 to PHP 8.2.26 then the CRM showed a error 500 because of PHP version.
I did a PHP downgrade and the CRM worked fine again.
I did a update from 4.5.2 to 4.5.4 and then I was able to update also PHP to 8.2.26
Later a new notice showed that I could update to 5.12.0 and I did it too.

Everything seems to work fine but somehow I see this red warning at the left bottom :
"Version 5.0.0 has been released, but it requires PHP 8.x "

Maybe have I missed something ?
Could it be a cache issue because I need to make the CRM update using still PHP 7.4 ?

Many thanks in advance.

[DAcodedBEAT]

Hello @dixitalmedia

ChurchCRM doesn't really have a caching mechanism in place but it's definitely possible that your machine does have one set up. Let's try to debug this together:

1. Check PHP Version

• Use ChurchCRM's debug page to confirm PHP >=8.1 is active.
• Alternatively, create a phpinfo.php file with the following content:

  <?php phpinfo(); ?>

  Access the file via the browser to check the PHP version.

2. (if selfhosted)Verify Apache + mod_php Configuration

• Ensure Apache is configured to use PHP 8.x by checking httpd.conf or related config files for:

  LoadModule php_module modules/libphp.so

• If necessary, enable mod_php for PHP 8.x.

3. Check .htaccess for PHP Version

• Ensure .htaccess (or any other configurations) don't specify an unsupported PHP (like PHP 7.4). For example, change or remove:

  AddHandler application/x-httpd-php74.php

  If present, update it to:

  AddHandler application/x-httpd-php84.php

4. Restart Apache

• After making changes, restart Apache to apply the new PHP configuration:

  sudo systemctl restart apache2

5. Confirm PHP 8.x Installation

• Run php -v to confirm PHP >=8.1 is installed.
• If PHP 8.x isn’t installed, install it with:

  sudo apt install php8.4 libapache2-mod-php8.4
  sudo systemctl restart apache2

6. Complete ChurchCRM Update

• Ensure the update to ChurchCRM 5.12.0 was applied correctly and there are no leftovers from previous versions that could cause confusion.