Problem after upgrade from 4.10 to 4.12 with russian lang

[sgtraf]

Hello  friends!
After  upgrade from  4.10 to 4.12   browser  displayed  error:

Parse error: syntax error, unexpected T_STRING in /home/gadz1/public_html/photo/lang/russian.php on line 66

I'm rename english.php to russian.php   for working my photo galery, but all words in gallery english.
How  made my gallery russian language without errors?

[Nibbler]

Download the fixed version from here.

[sgtraf]

thanks

Download the fixed version from here.

[henry]

Thanks for your response:

Download the fixed version from here.

Could you say a little more about applying the fix?  Is this a straight file substitution for the existing file in version 1.4.12, which is what my web hosting service installed automagically (via Fantastico)?   I guess it's

       ..<install-path>/lang/russian.php

that I'd be replacing, yes?

TIA,

Henry

[Sami]

Yes
Don't use auto-installer , such as fantastico it's buggy and outdated
1.4.12 is XSS vulnerable , download 1.4.13 from above download link and install it your self

[vovkas]

Hello 
After upgrade Coppermine galery to 1.14.44 happened problem with russian text from databese (not language, i'm use fixed version langfile)

i'm tried change Default and Unicide (utf-8) but does not help

Look attach

[Joachim Müller]

Post a link to your gallery.

not language, i'm use fixed version langfile

You're using what? If you use a customized language file (another one than the language file that comes with coppermine), then seek support from the person who provides that file.

[vovkas]

Hi!
I am use that file -

Download the fixed version from here.

But problem with Russian text from MySQL Like - Russian filename, Russian category name or Russian comment.

[Joachim Müller]

Post a link to your gallery.

[vovkas]

it version  for test  http://mgrt.msk.ru/foto2/index.php

[vovkas]

solution for Cyrillic 1251

coppermine\include\functions.inc.php:
After

Code Select Expand

$result = @mysql_connect($CONFIG['dbserver'], $CONFIG['dbuser'], $CONFIG['dbpass']);

Add

Code Select Expand

mysql_query("SET NAMES cp1251", $result);

And use russian.php in Cyrillic 1251

Info http://www.simplemachines.ru/index.php/topic,1267.msg8752.html#msg8752

[Joachim Müller]

That's nonsense - not related to this thread and simply not correct. Using a proprietary encoding (cp1251) instead of utf-8 is not recommended. Can't read the thread you refered to, as it is in Russian. The meta discussion about coppermine on the SMF board is not very relevant in my opinion. We (the coppermine dev team) consider the SMF project and their board to be a valid and usefull resource. However: the SMF staff is not an authority on coppermine-related issues.
The Russian language file in cpg1.4.12 contained a bug - it has been added last minute by the Russian translator before the release. It has been my mistake not to have review the last minute contribution before packaging cpg1.4.12, for which I have apologized. The broken Russian language file in cpg1.4.12 has been one of the reasons why cpg1.4.13 had to be released. Most recent stable release currently is cpg1.4.14, so this discussion about cpg1.4.12 simply is invalid. Nobody should install cpg1.4.12 any longer, so this entire discussion doesn't make sense.

I understand that you're trying to help others, but you draw false conclusions, so I'm posting this not for the sake to correct you, but as a reference for others with similar issues. Russian users: please don't let yourself get drawn into the false assumption that you should use proprietary encoding. Use unicode (aka utf-8) - it's the future.

[vovkas]

Use unicode (aka utf-8) - it's the future.

Convert MySQL database cp1251 to utf-8 ??

[Joachim Müller]

If you store utf-8 encoded data in those tables: yes.

[vovkas]

Why ver.1.2.1 work correct on my server but 1.4.14 not?

Code Select Expand


[b]3.1.2 Upgrading from cpg1.1.x, cpg1.2.x or cpg1.3.x to version cpg1.4.x[/b]
First, make a backup (dump) of your database.
Backup your include/config.inc.php file, your anycontent.php file and your "albums" directory.
Unpack the archive
Except for the "albums" directory, upload all of the new files and directories making sure not to overwrite the include/config.inc.php file, your anycontent.php file or the albums directory.
Delete all leftover, outdated language files in the lang folder
If you have not already done so, create a folder called "edit" within your "albums" directory - this folder will be used by coppermine as a temporary folder, do not ftp-upload files there. Make sure the new "edit"-folder is CHMODed the same way your albums-directory is (755 or 777, depending on your server's config)
Run the file "update.php" in the coppermine directory once in your browser (e.g. http://yourdomain.tld/coppermine/update.php). This will update your coppermine install by making all necessary changes in the database.
If you have made a custom theme, apply the changes that were introduced in the themes structure to your custom-made theme - refer to the theme-upgrade guide.
You can not use language files from older versions of Coppermine as primary language (the language the admin will use) - make sure you only have the language files that come with this package inside of your lang folder (delete or rename all files from older versions within the lang folder).
If you need to use a language that hasn't been translated for cpg1.4.x, you can try using the language file from cpg1.3.x, however there are certain caveats:

nothing about cyrillic-1251 and utf8

may i upgrading my Gallery correctly?

[Irinovna]

i am having the  same problem with my users. And i also had the program come with the hosting. How should i Apply the Code? you provided to fix it? Should i just replace it?