After Upgrade from 1.3..3 I run check version and get LOTS of Red Files After Upgrade from 1.3..3 I run check version and get LOTS of Red Files
 

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 Upgrade from 1.3..3 I run check version and get LOTS of Red Files

Started by bigfanboy, December 29, 2006, 12:02:39 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bigfanboy

I have upgraded from 1.3.3 to 1.4.10.

When I run the Check Version I get red on files that absolutely been upgraded and changed. To test this I have ftped individual files and rerun the Check Version and they still come up Red.

Any thoughts?


bigfanboy

I have also created a new test user cpgtest with password cpg123, but that user does not seem to log on. No error, just stays as guest after login.

Errrrr?

bigfanboy

I had another note, not sure if this is relavent. All the tables have the prefix cpg133_ and I thought I saw something that said CPG 1.4.10 assumes cpg_

??



Joachim Müller

Post a condensed screenshot of your versioncheck output as well.

bigfanboy

Not sure what you mean by condensed, so here is a cropped top half of the check version.


Joachim Müller

You can savely ignore that screen - versioncheck doesn't work on all setups, especially if the coppermine folder equals the web root.

I modified your posting to attach the screenshot to your posting instead of linking it (in case the link goes down later).

m@rk

I have exactly the same problem since I updated from v1.4.9 to 1.4.10.
But everythig works fine.

The clue is:

Version Check works properly with an identical installation under XAMPP test environment; the "everything's red problem" occurs only on my "live site".

I guess this must be related with some php global settings.
I could post both php-info's here if that might help to solve this problem?

Joachim Müller

If you have "allow_url_fopen" turned off on your live system, you will experience the above mentioned issues. That's why you should then un-tick the checkbox "try connecting to the online repository" to circumvent this.