Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: Switching from PHP 5.6 to 7.3  (Read 10598 times)

0 Members and 1 Guest are viewing this topic.

SunDancerGE

  • Coppermine newbie
  • Offline Offline
  • Posts: 1
Switching from PHP 5.6 to 7.3
« on: August 29, 2019, 02:43:18 pm »

Hi,

I have two instances of CPG installed. Both the current 1.6.0.6 version. In my admin back end of my hoster I switched both domains from PHP 5.6 to 7.3. One CPG is working just fine, the other one throws an error as long as I keep it on 7.3. On 5.6 it still works fine.

Code: [Select]
Fatal error: Uncaught Error: Class 'mysqli' not found in /home/www/doc/15877/oldenburger-spieletage.de/www/include/database/mysqli/dbase.inc.php:31 Stack trace: #0 /home/www/doc/15877/oldenburger-spieletage.de/www/include/init.inc.php(172): CPG_Dbase->__construct(Array) #1 /home/www/doc/15877/oldenburger-spieletage.de/www/index.php(22): require('/home/www/doc/1...') #2 {main} thrown in /home/www/doc/15877/oldenburger-spieletage.de/www/include/database/mysqli/dbase.inc.php on line 31
I bet this is something really simple but I can't wrap my head around it. Please help.
Logged

ron4mac

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: us
  • Offline Offline
  • Posts: 1344
Re: Switching from PHP 5.6 to 7.3
« Reply #1 on: August 29, 2019, 07:36:55 pm »

There must be some different PHP configuration changing files (php.ini .htaccess) in the path to the two galleries.

Put a small file in each gallery's root folder...

pinfo.php
Code: [Select]
<?php phpinfo(); ?>
Access the files from a browser. Look for differences that would keep one from providing the mysqli extension to PHP.
Logged
Pages: [1]   Go Up
 

Page created in 0.096 seconds with 20 queries.