Advanced search  

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]

Pages: 1 2 3 [4] 5 6 7 8 ... 10
 31 
 on: May 22, 2020, 02:21:53 am 
Started by BusAmerica - Last post by BusAmerica
Hello, and repeat my gratitude for the CPG develop team, and your work and thought.

Would be a good possibility of the CPG allow to incorporate:

1) More custom fields

For ejample of my site:

Now
Quote
(field1) CARROCERIA ( Marca / Modelo ): CAMETAL / JUMBUS

The ideal
(field1) CARROCERIA ( Marca ): CAMETAL
(field2) CARROCERIA ( Modelo ): JUMBUS

2) More custom sub files

Now
Quote
(field1) CARROCERIA ( Marca / Modelo ): CAMETAL / JUMBUS

The ideal
(field1) CARROCERIA ( Marca ): CAMETAL
(sub field2) CARROCERIA (marca) >> CARROCERIA ( Modelo ): JUMBUS

The field 2 insert in field 1

Like this site, who processing millions of images:
https://onibusbrasil.com/modelos/carroceria/cametal/jumbus (similary field 2)
https://onibusbrasil.com/modelos/carroceria/cametal (similary field 1)

Thanks again
Best regards

 32 
 on: May 22, 2020, 01:49:43 am 
Started by ErikM - Last post by BusAmerica
Hello.

The time passed.
I prefer the tablet sistem, but in the present the people access with your smartphone, and prefer "responsive sistem" than the scroll with your finger.

I adhere to this petition, now is very actuality, (and very complicated).

Thanks a lot for all the works of the actuality CPG team, and for the old CPG team.

****

Hola.

El tiempo pasó.
Prefiero el sistema de tableta, pero en la actualidad las personas acceden con su teléfono inteligente y prefieren el "sistema Responsive" que el scroll con sus dedos.

Me adhiero a esta petición, ahora es muy actual (y muy complicada).

Muchas gracias por todos los trabajos del equipo actual de CPG y al antiguo equipo de CPG.

 33 
 on: May 22, 2020, 01:25:33 am 
Started by juverci - Last post by BusAmerica
It would put the name of the author photo on the left, along with watermark in blue.
See example photo.

I adhere to this request.
It's very util, and I mean It's only one step more, than the CPG watermark present.
The example is very good about we need

****
Me adhiero a esta solicitud.
Es muy útil, y quiero decir que es solo un paso más que la marca de agua CPG presente.
El ejemplo es muy bueno sobre lo que necesitamos

 34 
 on: May 22, 2020, 12:36:06 am 
Started by FrA1l3 - Last post by BusAmerica
Thanks Ron.

You are the one who knows, so I 'll follow your advice. I do it since 2008, when I created the gallery.
But with these metod I don't order , like subfiles, the different characteristics

Now
Quote
(field1) CARROCERIA ( Marca / Modelo ): CAMETAL / JUMBUS

The ideal
(field1) CARROCERIA ( Marca ): CAMETAL
(field2) CARROCERIA ( Modelo ): JUMBUS

Complemented with an order system, which allows grouping all: (field2) CARROCERIA ( Modelo )
The field2 insert in field 1

Like this site, who processing millions of images:
https://onibusbrasil.com/modelos/carroceria/cametal/jumbus (similary field 2)
https://onibusbrasil.com/modelos/carroceria/cametal (similary field 1)

I'll post my wish, in "Feature Requests".
And 'll follow your advice.

Very thankful
Best regards

 35 
 on: May 21, 2020, 06:50:03 pm 
Started by FrA1l3 - Last post by ron4mac
There are many files in the CPG package that would need to be modified to successfully add and manage more custom user fields for images. And the fields would actually need to be added to the database. And all those changes would need to be done again after a CPG update.

You might consider doubling or tripling up on using what custom fields there are.
Instead of:
Quote
(field1) Make: Chevrolet
(field2) Model: Impala
(field3) Year: 1995
(field4) Color: Maroon
image info could be entered as:
Quote
(field1) Car: 1995 | Chevrolet | Impala | Maroon
And, if it is a matter of being able to search, it would be much easier to improve search capability than to make all the modifications needed for additional custom fields.

That all said ... if there were to be a significant outpouring of users requesting a variable number of custom fields, it could be worked into a future release.

 36 
 on: May 21, 2020, 05:58:06 pm 
Started by FrA1l3 - Last post by BusAmerica
Hello, and sorry if i have to open a new thread on this same topic. I take the CPG 1.6.x

*I modified code in
displayimage.php (in line 181)
with:
        for ($i = 1; $i <= 10; $i++) {

*And I modified
include/functions.inc.php (in line 1356)
with:
        for ($i = 1; $i <= 8; $i++) {

Like ron4mac gentily explicate, but not extra fields appears.

Is necessary to modified, like the olds CPG versions, all of these files (like Doggy expained: https://forum.coppermine-gallery.net/index.php/topic,35263.0.html) ?

    db_input.php
    editOnePic.php
    editpics.php
    lang/english.php
    lang/french.php
    image_processor.php
    include/picmgmt.inc.php
    include/search.inc.php
    thumbnails.php
    upload.php
    xp_publish.php


Thanks in advance
Best regards

 37 
 on: May 20, 2020, 07:00:16 pm 
Started by tbax1 - Last post by Phill Luckhurst
I think 2.01 is the only version that does work with 1.6.x

 38 
 on: May 19, 2020, 02:37:48 pm 
Started by tbax1 - Last post by ron4mac
Up
Others are successfully using v2.0.1 of CPM Fetch with CPG 1.6.  Based on your experience with the HideMyPics plugin, you may want to examine the configuration of PHP on whatever system you are using for your gallery.

Note: You'll probably find you get better help by providing a link to your gallery.

 39 
 on: May 19, 2020, 02:32:30 pm 
Started by ron4mac - Last post by ron4mac
See updated version (1.1) of the HideMyPics plugin:
https://forum.coppermine-gallery.net/index.php/topic,80066.msg387786.html#msg387786

 40 
 on: May 19, 2020, 03:24:01 am 
Started by tbax1 - Last post by tonyyears
Up

Pages: 1 2 3 [4] 5 6 7 8 ... 10

Page created in 0.016 seconds with 17 queries.