After upgrading from 1.4.18 to 1.4.19 coppermine still indicates 1.4.18 version After upgrading from 1.4.18 to 1.4.19 coppermine still indicates 1.4.18 version
 

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]

Main Menu

After upgrading from 1.4.18 to 1.4.19 coppermine still indicates 1.4.18 version

Started by Griffon, August 17, 2008, 05:16:27 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Print
Go Down Pages1
User actions

Griffon

August 17, 2008, 05:16:27 PM
I have performed a full upgrade as instructed in cpg1419/docs/index.html from 1.4.18 to 1.4.19.
The upgrade was successful and didn't throw any errors.

However when I checked the version of my coppermine in the configuration panel it indicates that it still 1.4.18:
(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fimg244.imagevenue.com%2Floc48%2Fth_86008_capture_122_48lo.JPG&hash=8c045db3e80970de783c9c11d8623bf119b49770)

Do you know what could be the problem?
Thanks :)

Nibbler

#1
August 17, 2008, 05:18:24 PM
You didn't upload include/init.inc.php. See versioncheck.php

Griffon

#2
August 18, 2008, 08:11:53 AM
Right you are, thanks :)

It now indicates in the config tab that my version is 1.4.19, however
when I run versioncheck.php I see the following page:
(https://coppermine-gallery.com/forum/proxy.php?request=http%3A%2F%2Fimg158.imagevenue.com%2Floc691%2Fth_39402_capture2_122_691lo.JPG&hash=6266158caa1c4b7b0b546a77497addce0cfc0bcc)

Almost all my files are marked in red.
It also says that it can't connect to the repository, does it mean that I can't rely on the results of the version check?

I used FileZilla to upload the entire cpg1419 directory (without the albums folder and the other files that the manual indicated not to override), maybe FileZilla didn't upload files with the same name, or with same size.
Can I now re-upload those files again?
Should I run update.php again after uploading those files?

Griffon

#3
August 20, 2008, 04:53:10 PM
Should I re-upload those files and run update.php?
Because right now I'm not sure if my site has the security vulnerability fixed or not.

Thanks :)

Nibbler

#4
August 20, 2008, 05:56:32 PM
Reupload anything that's in red. You don't need to run update.php in any case.

Griffon

#5
August 21, 2008, 03:26:06 PM
I have re-uploaded everything in red, and now versioncheck.php indicates that all is ok.

However I found out that the update.php that I ran before was also from version 1.4.18, should I run it again? (I know I asked you this before but since the update.php file itself is outdated then maybe necessary updates to the db were not made).

Sorry for the constant questions, I really appreciate your help.

Αndré

#6
August 21, 2008, 03:32:03 PM
It doesn't hurt, if you run update.php again.
Print
Go Up Pages1
User actions