Advanced search  

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

Pages: [1]   Go Down

Author Topic: I have problem with charset after upgrading from 1.4  (Read 3833 times)

0 Members and 1 Guest are viewing this topic.

kuzmitch

  • Coppermine newbie
  • Offline Offline
  • Posts: 4
I have problem with charset after upgrading from 1.4
« on: July 31, 2010, 01:33:54 pm »

Hello,

i've just made an upgrade from 1.4 to 1.5. Most of my albums vere named in ukrainian (cyrillic) - after upgrade - i have problems with albums names - only signs instead of cyrillic letters.....

Logged

kuzmitch

  • Coppermine newbie
  • Offline Offline
  • Posts: 4
Re: I have problem with charset after upgrading from 1.4
« Reply #1 on: July 31, 2010, 02:15:43 pm »

P.S.

MySQL charset:  UTF-8 Unicode (utf8)
db collation: latin1_swedish_ci
Logged

kuzmitch

  • Coppermine newbie
  • Offline Offline
  • Posts: 4
Re: I have problem with charset after upgrading from 1.4
« Reply #2 on: August 09, 2010, 07:23:58 pm »

so? nobody can help??? :(
Logged

phill104

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4886
    • Windsurf.me
Re: I have problem with charset after upgrading from 1.4
« Reply #3 on: August 09, 2010, 08:22:02 pm »

A link might help ;)
Logged
It is a mistake to think you can solve any major problems just with potatoes.

kuzmitch

  • Coppermine newbie
  • Offline Offline
  • Posts: 4
Re: I have problem with charset after upgrading from 1.4
« Reply #4 on: August 10, 2010, 10:45:32 am »

Logged

Αndré

  • Administrator
  • Coppermine addict
  • *****
  • Country: de
  • Offline Offline
  • Gender: Male
  • Posts: 15764
Re: I have problem with charset after upgrading from 1.4
« Reply #5 on: September 02, 2010, 11:24:39 am »

Please upgrade to cpg1.5.8. Then read this topic. I'm not sure if it solves your problem when you use the new dbcharset mechanism.
Logged
Pages: [1]   Go Up
 

Page created in 0.016 seconds with 20 queries.