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]   Go Down

Author Topic: specify keyword delimiter  (Read 5725 times)

0 Members and 1 Guest are viewing this topic.

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
specify keyword delimiter
« on: October 26, 2003, 12:01:08 pm »

Currently, the keywords can only be separated by spaces. In a future version I'd like to have the option to specify the keyword delimiter in the config page.
There has been a discussion on this on the old board, please refer to http://coppermine.sourceforge.net/oldboard/viewtopic.php?t=1914
Please also take into account the "umlauts" problem.

Anyone of the dev team wants to volunteer on this issue?

GauGau
Logged

Tarique Sani

  • VIP
  • Coppermine addict
  • ***
  • Offline Offline
  • Gender: Male
  • Posts: 2712
    • http://tariquesani.net
specify keyword delimiter
« Reply #1 on: October 26, 2003, 12:08:53 pm »

Err... future version <> 1.2.0 OR I am worng?
Logged
SANIsoft PHP applications for E Biz

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
specify keyword delimiter
« Reply #2 on: October 26, 2003, 12:14:53 pm »

hehe, any dev version is fine by me;
I was just trying to clarify that this won't go into the cpg1.2.0Final :wink:

GauGau
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
specify keyword delimiter
« Reply #3 on: October 26, 2003, 12:18:05 pm »

just to get an idea: I've already included the hack from the old board into my existing install, but there's a problem with the Umlauts - see http://www.gaugau.de/galerie/displayimage.php?pos=-3422 as an example (look at the keyword section)...

GauGau
Logged

Tarique Sani

  • VIP
  • Coppermine addict
  • ***
  • Offline Offline
  • Gender: Male
  • Posts: 2712
    • http://tariquesani.net
specify keyword delimiter
« Reply #4 on: October 26, 2003, 12:19:35 pm »

OK I will look into this sometime next week...

P.S. Wife looked over the shoulder and wants to know the mystery behind the word "Gaugau"
Logged
SANIsoft PHP applications for E Biz

Tarique Sani

  • VIP
  • Coppermine addict
  • ***
  • Offline Offline
  • Gender: Male
  • Posts: 2712
    • http://tariquesani.net
specify keyword delimiter
« Reply #5 on: October 26, 2003, 12:49:12 pm »

Quote from: "gaugau"
just to get an idea: I've already included the hack from the old board into my existing install, but there's a problem with the Umlauts


Line 248 the regex /(\S+)/  - what did you replace that with?
Logged
SANIsoft PHP applications for E Biz

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
specify keyword delimiter
« Reply #6 on: October 26, 2003, 01:11:04 pm »

currently, the regex is
Code: [Select]
       $info[$lang_picinfo['Keywords']]   = '<span class="alblink">'.preg_replace("/(\w+)/","<a href=\"thumbnails.php?album=search&search=\\1\">\\1</a>" , $CURRENT_PIC_DATA['keywords']).'</span>';

@Swati: "GauGau" is my nickname - it's pronounced like "gow gow" (like "cow", only with "g"). My "realname" is "Joachim", which is a common German name, often nicknamed "jojo" (hear pronounciation). This has changed (during school) over "jaujau" to "gaugau" (I didn't choose this name!). First I wasn't to happy with this nickname, but people hardly know me by my realname, so I got used to it (see this in detail on the German page http://gaugau.de/specials/faq/gaugau.htm )

GauGau
Logged
Pages: [1]   Go Up
 

Page created in 0.025 seconds with 20 queries.