prop_name with international characters problem

[liudaz]

Hello,

The first time i've got this problem, i didn't pay any attention. The second time i got this problem on different database and CMS version, i took some time to investigate.
The thing is, that is that i create prop_name with international characters, like ąčęėįšū, i can't put any value into the content column at the content_props table.
This happens becouse when i try to add content content, cms retrieves prop_names from the database in wrong encoding.

Let me give you an example. I have installed a cataloger module. And i created a user defined attribute with name lets say "ąčęėėįįššųūųū9". Than i go to add a new catalog item, i write something in the input box, that should be named "ąčęėėįįššųūųū9" and submit it. I go to check the databe, and the field at the "content" column appears to be blank.

I checked the source of the admin panel, where i add new catalog item. You can see it here http://armindina.lt.mamutas.serveriai.lt/images/band/prop.gif. You see the question marks  at the input name?
I believe this has to be something with the encoding... right?

I had the same problem when useing form building module: i create an input form and name it with international characters. I have tested this on CMS MS MLE 1.0.2 build4 and CMS MS 1.0.4

Please pardon me for my language and explaining this "bug" in such difficult way.

Any suggestions, comments or tips, how this could be solved would be appreasiated.
If there is something i could say to make it more easy to understand, please, let me know.

Sincerely,
Liudas

[liudaz]

I hate to bring this up, but... "bump"... can't figure out what to do...
Any help would be very appresiated.


Liudas

[Elijah Lofgren]

I don't really know any easy way to fix this other than to just use English.

I guess you could file some bugs in the bug tracker on the forge.

Also, maybe ask in the #cms channel on irc.freenode.net and see if anyone there is able to help.

Sorry I can't be of help,

Elijah

[cyberman]

Are you sure your charset encoding is right?

I'm not very familiar with cataloger. Maybe you should try to call cataloger via smarty tag, not via content type.

[liudaz]

Thank you Elijah. i appreasiate your help.

Are you sure your charset encoding is right?

I'm not very familiar with cataloger. Maybe you should try to call cataloger via smarty tag, not via content type.

If i want to add data into the catalog, i have to use admin panel and i don't really know any other way of doing this via smarty tags. When displaying data... smarty tags wouldn't change anything, bcouse the cells at the database are empty.
All the possible encoding types and properties are set to UTF-8. Never had this problem on any other modules or content types. Calguy1000 said he was going to take a look at this. So there is still some hope

[karry]

Any news on this subject? I have the same problem with danish characters, and would like to hear if there is a solution.

[liudaz]

I partially solved this problem for my project by doing theese steps:
1. created the attributes with those "bad" international characters
2. found the CMS database table cells, where the definitions of attributes are stored
3. edited those cells: replaced the "bad" characters with the symbol codes like this: čėęčį

This is really tricky. If after editing the databese, you come back to the admin panel and hit "submit attributes", you have to repeat 3rd step again.

It is just a work around, but for my case (only several attributes) it worked.

[karry]

Thanks, that helped me a lot!,  though its only a half solution