- Welcome to coppermine-gallery.com/forum.
Recent posts
#21
cpg1.6 install / Re: PHP 8
Last post by FrA1l3 - August 07, 2025, 12:42:23 PM #22
cpg1.6 install / Re: PHP 8
Last post by FrA1l3 - August 07, 2025, 12:41:10 PMQuote from: phill104 on August 06, 2025, 11:44:06 PMI would also think it is worth checking what the 500 error actually is. You would need to either enable error reporting or check the server logs to do that. It could be a number of things that are easy to resolve.
Thanks, yes, you've given me an idea, and after checking, I've seen that it simply fails when I have the ron4mac user2FA plugin enabled.
If I enable it, it won't let me log in, although the gallery works correctly. I've even tried logging in with PHP 7.4, upgrading to 8.4, and in the same session, if I'm logged in, I'm fine, and it lets me change options and everything.
But when I try to log in, it won't let me, so the problem is with the plugin.
I can't find the right url for the plugin, I've installed v1.1, comes from here: https://coppermine-gallery.com/forum/index.php/topic,80370.0.html
thank you so much
#23
cpg1.6 install / Re: PHP 8
Last post by phill104 - August 06, 2025, 11:44:06 PMI would also think it is worth checking what the 500 error actually is. You would need to either enable error reporting or check the server logs to do that. It could be a number of things that are easy to resolve.
#24
cpg1.6 install / Re: PHP 8
Last post by 406man - August 06, 2025, 08:59:32 PMThe new Coppermine 1.6.27 is meant to work with PHP 8.4. I've not tried it myself yet.
#25
cpg1.6 install / Re: PHP 8
Last post by FrA1l3 - August 06, 2025, 01:41:00 AMSorry guys, I saw this is for a clean install.
I have shared hosting, and within it, I have a WP installation and a Coppermine installation. The thing is, upgrading from PHP 7.4 to any version of 8.x ends up with a 500 error when using Coppermine.
If I roll back the version, everything works fine.
The issueis that both WP and the hosting people are telling me that I should upgrade to PHP 8.4 due to the security risks of using an older version like PHP 7.4.
On WP, I have a store (WC) with personal data, and I wouldn't like to put that information at risk. So, is there any way I can explore the option of migrating to PHP 8.4, for example, and still have Coppermine work?
Since it's an installation on a shared server, I can barely touch the PHP configuration, as this guy indicated in the thread.
I'm quite concerned about security.
Thank you very much!
I have shared hosting, and within it, I have a WP installation and a Coppermine installation. The thing is, upgrading from PHP 7.4 to any version of 8.x ends up with a 500 error when using Coppermine.
If I roll back the version, everything works fine.
The issueis that both WP and the hosting people are telling me that I should upgrade to PHP 8.4 due to the security risks of using an older version like PHP 7.4.
On WP, I have a store (WC) with personal data, and I wouldn't like to put that information at risk. So, is there any way I can explore the option of migrating to PHP 8.4, for example, and still have Coppermine work?
Since it's an installation on a shared server, I can barely touch the PHP configuration, as this guy indicated in the thread.
I'm quite concerned about security.
Thank you very much!
#26
cpg1.6 upgrading / Re: Date format corrupt after ...
Last post by Aurel Klatik - August 03, 2025, 09:03:44 PMthank you
I have updated lang/Slovak.php
it works with local date formats
use as is or edit lines 43 thru 50 as required
I have updated lang/Slovak.php
it works with local date formats
use as is or edit lines 43 thru 50 as required
#27
cpg1.6 upgrading / Re: Date format corrupt after ...
Last post by 406man - August 03, 2025, 06:04:50 PMDate formats changed with version 1.6.
The way dates and times are displayed is defined in the language files. It seems that the language files for Slovak and many other languages have not been updated to suit the change.
The file that needs to be changed is slovak.php in the lang folder. Around lines 43 to 52 are the various definitions.
Definitions in the new format can be found in english.php
Hopefully you can use them to figure out what they need to be in the Slovak language. Use something like Windows Notepad to make the change. I use the free pspad editor which is excellent.
When you've finished perhaps you could attach the finished version of slovak.php here so the developers can add it to the next release.
The way dates and times are displayed is defined in the language files. It seems that the language files for Slovak and many other languages have not been updated to suit the change.
The file that needs to be changed is slovak.php in the lang folder. Around lines 43 to 52 are the various definitions.
Definitions in the new format can be found in english.php
Hopefully you can use them to figure out what they need to be in the Slovak language. Use something like Windows Notepad to make the change. I use the free pspad editor which is excellent.
When you've finished perhaps you could attach the finished version of slovak.php here so the developers can add it to the next release.
#28
cpg1.6 upgrading / Date format corrupt after upgr...
Last post by Aurel Klatik - August 02, 2025, 08:53:14 PMI have upgraded from CPG 1.5 to 1.6 and found the date format changed everywhere and displays like this:
%06. %922 %2025
Language is set Slovak
Character set is Unicode (utf-8)
I have not found where date format setting might be.
Any hint much appreciated.
%06. %922 %2025
Language is set Slovak
Character set is Unicode (utf-8)
I have not found where date format setting might be.
Any hint much appreciated.
#29
cpg1.6 upgrading / Re: Unable to connect to datab...
Last post by Aurel Klatik - August 02, 2025, 08:09:02 PMProblem solved. Thank you for your support.
It was unable to connect to database because of password did not meet requirements (capital letter, number ...)
In PHP5 with CPG 1.5 it worked, but after switching to PHP8 for CGP 1.6 update it didn't.
Finally database password change solved the problem.
I have upgraded to CPG 1.6 successfully.
It was unable to connect to database because of password did not meet requirements (capital letter, number ...)
In PHP5 with CPG 1.5 it worked, but after switching to PHP8 for CGP 1.6 update it didn't.
Finally database password change solved the problem.
I have upgraded to CPG 1.6 successfully.
#30
cpg1.6 plugin contributions / Re: Suppressor Plugin
Last post by 406man - July 30, 2025, 04:40:42 PMI'm releasing version 1.2.1 of the Suppressor plugin which is a maintenance release. There were a few bugs, features and limitations in version 1.2 which I've addressed.
Here is a more detailed description. The previous version 1.2 suppressed the uploader name when thumbnails were displayed in a standard album but there were other albums where the uploader name was still displayed. For example, displaying the most recent uploads would display all the uploader names. In the case of, for example, a competition where you wanted to keep the names of the entrants secret this would have allowed the names to be displayed. When displaying the uploads for a particular member using the link in their profile the display of the image thumbnail, title and upload date would allow the identity of an uploader to be figured out. So Version 1.2.1 suppresses all relevant details. This applies in keyword albums and all relevant meta albums and . In the case of displaying the uploads for a particular member the thumbnail itself is replaced by a "security" thumbnail. If the user viewing the images is an administrator all the details are displayed - in other words nothing is suppressed.
Here is a more detailed description. The previous version 1.2 suppressed the uploader name when thumbnails were displayed in a standard album but there were other albums where the uploader name was still displayed. For example, displaying the most recent uploads would display all the uploader names. In the case of, for example, a competition where you wanted to keep the names of the entrants secret this would have allowed the names to be displayed. When displaying the uploads for a particular member using the link in their profile the display of the image thumbnail, title and upload date would allow the identity of an uploader to be figured out. So Version 1.2.1 suppresses all relevant details. This applies in keyword albums and all relevant meta albums and . In the case of displaying the uploads for a particular member the thumbnail itself is replaced by a "security" thumbnail. If the user viewing the images is an administrator all the details are displayed - in other words nothing is suppressed.