Versioncheck reports modified Versioncheck reports modified
 

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

Versioncheck reports modified

Started by nickelas, April 06, 2010, 06:37:54 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

nickelas

When running a versioncheck it reports 18 potential issues. 17 (all but anycontent.php) are reported as modified.
Downloaded cpg 1.5.3 again, and uploaded docs/en/translation.htm from this, but it was still reported as modified.
Downloaded docs/en/translation.htm from the repository and then uploaded it. It was then reported as newer than expected. Means it should not be a ftp-problem, right? Using filezilla by the way.
uppsalafoto.se/galleri
Thanks
Human

nickelas

The reason for asking is that I am getting a wierd error. So I am wondering if the upgrade to 1.5.3 worked ok.
Is it normal that for instance register.php and include/functions.inc.php are reported as modified?
Human

Joachim Müller

cpg1.5.3 is a release candidate and not a stable release. The data for version check may or may not work. From the docs:
Quote from: http://documentation.coppermine-gallery.net/en/upgrading.htm#versioncheck_comparison_modifiedModified
If a file is accessible and the version and revision numbers match, the versioncheck script attempts to perform a check wether the file has been modified, compared to the original that comes with the coppermine package. This check is being performed by taking into account the MD5-hashes of the original file and your copy.
When performing a fresh install or upgrade, there should be no modified files. If they are being displayed as modified, there are several possible reasons:

    * You deliberately modified the file (e.g. by applying a custom modification to it). In this case, it's OK to ignore the warning in the "Modified"-column and continue
    * Your file has not been transfered fully to the webserver. If this is the case, try to re-upload the file from your client to the server. If this doesn't help, your package might have gotten corrupt. Re-download a fresh one from the coppermine download section, un-archive it and re-upload the file. Make sure that your FTP app is configured to actually overwrite existing files
    * You have used an improper FTP-mode to transfer the file to your webserver. Using FTP apps, you can transfer files in binary or ASCII-mode. Most up-to-date FTP clients have a feature that will automatically select the proper FTP-mode for each file. If this is not the case, try the manual appoach and explicitely specify the FTP-mode for your file uploads.
    * Your webhost is injecting code into each file. Many free webspace providers (so-called "freehosts") do this to inject advertisments into your files. There's little you can do then except signing up with paid webhosting or ignoring the "Modified"-warning and hoping that things will work anyway.

The output of the column "modified" can be filtered by enabling the option Don't check for modified files. This will result in a slightly increased performance of the versioncheck script.
Any of the mentioned reasons may apply. The version check feature is a tool, not a cause of problems. If it doesn't work for you or if you don't understand the impact of it, then please don't ask here.
In the other thread you refer to you have failed to describe what actually is wrong. Don't clutter your issues over the entire board. Start a thread with the actual issue and stick to it.