I suspect that the md5sum in cpg16x.files.xml for init.inc.php also needs to be updated in the repository.
Thanks, John ... corrected.
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]
31
on: February 04, 2024, 01:10:18 pm
|
||
Started by JohnDBush - Last post by ron4mac | ||
I suspect that the md5sum in cpg16x.files.xml for init.inc.php also needs to be updated in the repository. Thanks, John ... corrected. |
32
on: February 04, 2024, 10:31:50 am
|
||
Started by JohnDBush - Last post by JohnDBush | ||
Reinstallation using the stub solved the problem for the most part. Most of the errors no longer appear.
However, now Versioncheck reports that include/init.inc.php is either corrupt or was modified. I looked at its md5sum hash in cpg16x.files.xml, and it doesn't match the file. When I corrected the hash, Versioncheck still reports that the file is corrupt. Obviously it is NOT corrupt because everything works, and I did not modify init.inc.php. Line #5377 of cpg16x.files.xml: The incorrect hash was: 3cb6e66a5a4d5b33078d58fb7c46b48c The hash I replaced it with was: 521d42c772634747b266921e89c37472 <-- derived using md5sum include/init.inc.php No <Tags> were disturbed. Versioncheck still reported "File may be corrupt...", but when I re-ran it after selecting "Do not connect to the online repository", the discrepancy disappeared. I suspect that the md5sum in cpg16x.files.xml for init.inc.php also needs to be updated in the repository. |
33
on: February 04, 2024, 08:51:19 am
|
||
Started by JohnDBush - Last post by JohnDBush | ||
Many thanks!
|
34
on: February 03, 2024, 12:49:31 pm
|
||
Started by JohnDBush - Last post by ron4mac | ||
Yes, you can ignore them. There was an oversight in packaging the 1.6.26 release. It will be immediately corrected.
You can use the cpg_installer_stub to re-upgrade to 1.6.26, if you choose. |
35
on: February 03, 2024, 09:42:36 am
|
||
Started by JohnDBush - Last post by JohnDBush | ||
I upgraded from 1.6.20 to 1.6.26, ran database update, and Versioncheck.
Versioncheck says I now have version 1.6.25 installed, and produces the following discrepancies: (see attachment) There doesn't seem to be any problem with the gallery functioning, but I don't use all features. Can I ignore these errors? I'm thinking that perhaps it's an error with Versioncheck itself and not my installation. |
36
on: January 30, 2024, 08:47:32 am
|
||
Started by panhead - Last post by panhead | ||
Thank you!
|
37
on: January 29, 2024, 10:56:19 pm
|
||
Started by Joe Carver - Last post by Joe Carver | ||
This topic has been moved to cpg1.6 upload.
https://forum.coppermine-gallery.net/index.php?topic=80781.0 |
38
on: January 29, 2024, 10:55:26 pm
|
||
Started by joerobertson - Last post by Joe Carver | ||
See the Coppermine Photo Gallery v1.6.x: Documentation and Manual for:
Max size for uploaded files Server Side Restrictions Moving to cpg1.6 upload. |
39
on: January 29, 2024, 10:42:21 pm
|
||
Started by panhead - Last post by Joe Carver | ||
You could try to rename the file folder(s) so that Coppermine won't find them.
Or, copy the folder using your cPanel and then try the rename (better). Or, proceed only with a backup copy (best). |
40
on: January 27, 2024, 08:43:28 pm
|
||
Started by joerobertson - Last post by joerobertson | ||
I installed a new copy of the latest Coppermine on a new hosting acoount.
Im using the same file size info as in my previous install. When i try to upload a photo, i get the following: PXL_20240127_191103481[1].jpg File is larger than max size allowed I had this file on my previous site with no issues |