- Welcome to coppermine-gallery.com/forum.
News:
CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE
Recent posts
#41
cpg1.6 themes (visuals) / Re: Additional custom fields
Last post by FrA1l3 - January 28, 2025, 12:44:25 AMMods for 1.6.26
You need to use Fileseek for example and search for these words:
user4
user_field4_name
usr4
user_field
Other words to search (but you can find it with usr4 as well):
enabusr4
usr4fld
usr4checked
This is the list of files to modify to get 100% functionality on this version:
db_imput.php
edit_one_pic.php
editpics.php
thumbnails.php
uniload.php
update.php
search.php <-- change foreach (range(1, 4) for 1, 20
include/admin.inc.php
include/functions.inc.php <-- there is a 'for' for user_field limited to 4 fields replace with (( $i <= 20 ))
include/picmgmt.inc.php
include/search.inc.php
include/codebase.php
plugins/upload_h5a/admin.php
plugins/upload_h5a/config.php
plugins/upload_h5a/initialize.inc.php
plugins/upload_h5a/js/upload.js
plugins/upload_h5a/js/upload.min.js
plugins/upload_sgl/codebase.php
sql/schema.sql
sql/basic.sql
Additionally, you should modify your language file, in my case, I'm from Spain so I need to edit this file:
lang/spanish.php
You need to use Fileseek for example and search for these words:
user4
user_field4_name
usr4
user_field
Other words to search (but you can find it with usr4 as well):
enabusr4
usr4fld
usr4checked
This is the list of files to modify to get 100% functionality on this version:
db_imput.php
edit_one_pic.php
editpics.php
thumbnails.php
uniload.php
update.php
search.php <-- change foreach (range(1, 4) for 1, 20
include/admin.inc.php
include/functions.inc.php <-- there is a 'for' for user_field limited to 4 fields replace with (( $i <= 20 ))
include/picmgmt.inc.php
include/search.inc.php
include/codebase.php
plugins/upload_h5a/admin.php
plugins/upload_h5a/config.php
plugins/upload_h5a/initialize.inc.php
plugins/upload_h5a/js/upload.js
plugins/upload_h5a/js/upload.min.js
plugins/upload_sgl/codebase.php
sql/schema.sql
sql/basic.sql
Additionally, you should modify your language file, in my case, I'm from Spain so I need to edit this file:
lang/spanish.php
#42
cpg1.6 miscellaneous / Re: Error after updating to ph...
Last post by Joe Carver - January 27, 2025, 06:37:36 PMIt looks like you are running an older version of Coppermine.
Upgrade to version 1.6.26 (links above).
(from the release notes: "Line 56: 2020-02-25 [M] Remove use of deprecated *magic_quotes* functions {ron4mac}")
Upgrade to version 1.6.26 (links above).
(from the release notes: "Line 56: 2020-02-25 [M] Remove use of deprecated *magic_quotes* functions {ron4mac}")
#43
cpg1.6 miscellaneous / Error after updating to php 8....
Last post by sindbad5 - January 27, 2025, 03:05:44 PMFatal error: Uncaught Error: Call to undefined function get_magic_quotes_runtime() in /www/htdocs/w012fc80/medienarchiv.com/0/include/init.inc.php:63 Stack trace: #0 /www/htdocs/w012fc80/medienarchiv.com/0/login.php(21): require() #1 {main} thrown in /www/htdocs/w012fc80/medienarchiv.com/0/include/init.inc.php on line 63
https://www.medienarchiv.com/0/
This happened after setting PHP from 7.4 to 8.4 at my hoster. I can't get back to 7.4. Anyone knows how to solve this? Thanks!
#44
cpg1.6 upgrading / Re: Upgrade from 1.6.12 to 1.6...
Last post by phill104 - January 26, 2025, 12:27:32 AM #45
cpg1.6 upgrading / Upgrade from 1.6.12 to 1.6.26
Last post by JPNARF - January 22, 2025, 12:40:20 PMHi All,
I want to upgrade from 1.6.12 to 1.6.26.
My Actual configuration:
AlmaLinux 9.5
Kernel: Linux 5.14.0-362.24.2.el9_3.x86_64
Apache/2.4.62
PHP 7.4.33
MySQL 5.7.44
php-mysqlnd-7.4.33-10
I would like to know which are the lastest version of MySQL and PHP that can I use for version 1.6.26
Regards,
I want to upgrade from 1.6.12 to 1.6.26.
My Actual configuration:
AlmaLinux 9.5
Kernel: Linux 5.14.0-362.24.2.el9_3.x86_64
Apache/2.4.62
PHP 7.4.33
MySQL 5.7.44
php-mysqlnd-7.4.33-10
I would like to know which are the lastest version of MySQL and PHP that can I use for version 1.6.26
Regards,
#46
cpg1.6 upgrading / Re: Constant E_STRICT is depre...
Last post by 406man - January 05, 2025, 06:05:42 PMLine 95 of include/debugger.inc.php contains the constant E_STRICT in CPG 1.6.26
E_STRICT was deprecated in PHP 8.4
https://php.watch/versions/8.4/E_STRICT-deprecated
Reverting to a slightly older version of PHP will avoid the problem until the CPG code is updated.
E_STRICT was deprecated in PHP 8.4
https://php.watch/versions/8.4/E_STRICT-deprecated
Reverting to a slightly older version of PHP will avoid the problem until the CPG code is updated.
#47
cpg1.6 upgrading / Re: Constant E_STRICT is depre...
Last post by phill104 - January 05, 2025, 10:22:04 AMWhich version of CPG are you running
#48
cpg1.6 upgrading / Constant E_STRICT is deprecate...
Last post by AnnieHoney - January 04, 2025, 11:03:31 AMI'm getting several lines of these on index.php, not on other pages and only when I'm logged in
#49
cpg1.6 upload / Upload Image Size Bugs
Last post by 406man - December 29, 2024, 11:50:49 AMSeveral months back I changed some aspects of my gallery which included changing the maximum image size. What I want is for users to upload images that are a particular height or less. Images are not resized to be sure that what users see is what they uploaded. The gallery config doesn't allow me to set a maximum height and width as it's the maximum height that's important. I have to accept any width. I found that both the 1.6.26 single and multiple upload routines fail to validate the image size properly with this combination of config settings.
In more detail, bug 1 is that if the gallery config settings are:
"Auto resize images that are larger than max width or height" is unchecked
and "Use Dimension" is set to either "Height" or "Width"
... the validation works as if "Use Dimension" is set to "Max Aspect".
This means that if I upload an image that's 1600px wide by 1200px high with:
"Use Dimension" set to "Height"
and "Max width or height for uploaded pictures" set to 1200px
...it's rejected because the validation rejects an image that's wider than 1200px. It should ignore the width.
The bug is present when using both the single upload and h5 multiple upload methods.
To fix the bug I've created a new version of picmgmt.inc.php with additional code for a config where images are not resized.
Bug 2 is that the error message that's displayed by the single image uploader when an image is rejected due to being too big is displayed on an ugly blank white screen, not on a proper CPG screen. The error message displayed by the h5 multiple upload is fine.
To fix the bug I've created a new version of uniload.php which has a new section for handling an error in the single upload method. It redirects to the upload screen with a message box showing the error. To avoid having to update the language files the error message for a width that is too large isn't ideal in my updated version and says:
"The size of file you have uploaded is too large (maximum allowed is Height x 1200)!';
Ideally the error message text in english.php would be changed to:
'The file you have uploaded is too large. Should be: %s %s px'
...which after substitution looks like:
'The file you have uploaded is too large. Maximum: Height 1200 px'
For reference, the error variable is, in english.php:
$lang_db_input_php['err_fsize_too_large'] = 'The size of file you have uploaded is too large (maximum allowed is %s x %s)!';
Ideally the updated variable would be:
$lang_db_input_php['err_fsize_too_large'] = 'The file you have uploaded is too large. Maximum: %s %s px'
These changes have been working successfully for several months.
Revised versions of picmgmt.inc.php and uniload.php attached. As the forum doesn't allow me to upload a .php file I've added .txt as a file extension. I haven't changed english.php to avoid any conflicting edits with other changes.
I'm not asking for any support, only to include the fixes in the next release of CPG.
In more detail, bug 1 is that if the gallery config settings are:
"Auto resize images that are larger than max width or height" is unchecked
and "Use Dimension" is set to either "Height" or "Width"
... the validation works as if "Use Dimension" is set to "Max Aspect".
This means that if I upload an image that's 1600px wide by 1200px high with:
"Use Dimension" set to "Height"
and "Max width or height for uploaded pictures" set to 1200px
...it's rejected because the validation rejects an image that's wider than 1200px. It should ignore the width.
The bug is present when using both the single upload and h5 multiple upload methods.
To fix the bug I've created a new version of picmgmt.inc.php with additional code for a config where images are not resized.
Bug 2 is that the error message that's displayed by the single image uploader when an image is rejected due to being too big is displayed on an ugly blank white screen, not on a proper CPG screen. The error message displayed by the h5 multiple upload is fine.
To fix the bug I've created a new version of uniload.php which has a new section for handling an error in the single upload method. It redirects to the upload screen with a message box showing the error. To avoid having to update the language files the error message for a width that is too large isn't ideal in my updated version and says:
"The size of file you have uploaded is too large (maximum allowed is Height x 1200)!';
Ideally the error message text in english.php would be changed to:
'The file you have uploaded is too large. Should be: %s %s px'
...which after substitution looks like:
'The file you have uploaded is too large. Maximum: Height 1200 px'
For reference, the error variable is, in english.php:
$lang_db_input_php['err_fsize_too_large'] = 'The size of file you have uploaded is too large (maximum allowed is %s x %s)!';
Ideally the updated variable would be:
$lang_db_input_php['err_fsize_too_large'] = 'The file you have uploaded is too large. Maximum: %s %s px'
These changes have been working successfully for several months.
Revised versions of picmgmt.inc.php and uniload.php attached. As the forum doesn't allow me to upload a .php file I've added .txt as a file extension. I haven't changed english.php to avoid any conflicting edits with other changes.
I'm not asking for any support, only to include the fixes in the next release of CPG.
#50
cpg1.6 miscellaneous / Re: Deprecated: Automatic conv...
Last post by phill104 - December 12, 2024, 04:22:16 PMPlease upgrade to the latest 1.6.26 release