[Solved]: 1.4.17 > 1.4.18 - Patch applied, then run update.php? [Solved]: 1.4.17 > 1.4.18 - Patch applied, then run update.php?
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

[Solved]: 1.4.17 > 1.4.18 - Patch applied, then run update.php?

Started by isajade, April 14, 2008, 02:09:21 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

isajade

April 14, 2008, 02:09:21 PM Last Edit: April 14, 2008, 03:04:58 PM by Nibbler
Hi,

I am running  running 1.4.17 and just replaced the bridge/coppermine.inc.php file.
Do we also have to run update.php?

Thank you

Pascal YAP

#1
April 14, 2008, 02:54:38 PM
Yes you can, it's not dangerous  ;D
Maybe, after your Update you can rename only this file by update.php_ (or delete this one), if your afraid about an other potential attack.

PYAP

Nibbler

#2
April 14, 2008, 03:03:06 PM
There is no need to run update.php in this case, but it does no harm. It's used to apply changes to the database and there are no database changes in this release.

isajade

#3
April 14, 2008, 03:04:34 PM
Thank you for the replies.
Print
Go Up Pages1
User actions