DropDown editor, Improvements and a bug?

[eNZo]

Hi there, this might be the wrong Forum Topic, but i try.

I found what i think might be a few bugs.
Also want an improvement.

I will try to explain whats wrong.
I have installed Sugar 5.1 with Swedish Language Pack.

(x) = different screens

First thing, Improvement.
(1) When you go to the drop-down editor, all the "available" drop-downs are shown.
Ex. account_type_dom, activity_dom etc etc.
(2) Lets say click at account_type_dom, then i will enter that ones edit-area, with all the values, listed.
The language is in this case, still English..or what ever, that do not mater right now.
If is choose to "Add" a new one, i have to click Save, when i have entered the name, and label.
BUT... it takes me back the screen (1) !! What if i wanted to edit more...
So, maybe..a new button, for that. One for "save" and one for "Save & Done"

Here comes Bug 1:
Besides, if i enter exampel name: test and label test, click the "add" button, and then i click Save.
it takes me back (as i sad above to screen 1) if i now again enter the account_type_dom screen 2, it has also added a field called "empty" with label "empty".
And it keeps adding "empty" if i add ex. test2/test2,add, then save. and go back..its now 2 field empty.

Here comes Bug 2:
This has with the character "åäö, ÅÄÖ" to do.
Lets say i am at screen 2 at account_type_dom, and choose the language: SV Svenska (Swedish)
If i add ex:
Name: ovrig_kund Label: Övrig Kund
of curse click Add, and then Save, and then go back..(See improvements above)
It shows me:
Name: ovrig_kund Label: Ãvrig Kund
à where it should be an: Ö

Here is where the a sick bug appears: If i go in to that screen again, and just click Save (or if i add something and click add)
when i then go back, the sign "Ã" is doubled!,
Name: ovrig_kund Label: ÃÃvrig Kund
if i click save again, o add something, it gets duoubled again...
Name: ovrig_kund Label: ÃÃÃÃvrig Kund
This is the same when i use
å > Ã¥
ä > ä
ö > ö
Å > Ã…
Ä > Ä
Ö > Ä

In the end..i i change/add o few things..it would look ridicules
2 exampel:
Name: ovrig_kund
Label: ÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÂÃÃÂÃÂÖvrig Kund
Name: mojlighet
Label: MÃÂà ƒÂƒÃ‚‚¶jlighet/Utsikt

Hope you understand.
Any solutions?

Regards
eNZo

[jasv]

Hi!

Have you ever solved this bug????

I'm through this right now, and i don't know what to do!!!!

Hope you (Someone) can help me!!!! i'm using sugarcrm 5.1.0 and it has the same problem.

Salutes.

[mrmmm]

If you are referring to the non-standard characters being saved as gibberish in the DropDown list, then it is a known bug. It is logged in Sugar Bug tracker.
The way to get around this, is to manually edit the language file (custom/include/language/.......) and change/write in the values you need into the appropriate dropdown.

[veronicakatz]

I edited the file, but as soon as I edit the dropdown list via Studio again (for example: in order to add new values), the manually edited values get wrong again.
This happens with spanish accented vowels (á, é, and so on...).

I'm working with 5.1.0 + spanish language pack for 5.1.0 (recently released). Last week I worked with SLP 5.0.0f, and this happened the same, as well.

Verónica

[eNZo]

If you are referring to the non-standard characters being saved as gibberish in the DropDown list, then it is a known bug. It is logged in Sugar Bug tracker.
The way to get around this, is to manually edit the language file (custom/include/language/.......) and change/write in the values you need into the appropriate dropdown.

Thanks for that solution. That will do for now.
Do you have any link to the Sugar Bug tracker, regarding this case? Would be interesting to monitor it.

Regards
eNZo

[Rudi Mentär]

same problem here, i will try to edit them in the language file

[mrmmm]

I think there are several bugs related to this. For example: 24828, 24984.

[roblaus]

This problem still exists in 5.1a

[SugarDev.net]

Just a tip here: Using multibyte/non-standard characters as KEYS in dropdown menus seems unwise to me. I know it could work perfectly, but I'm hugely more comfortable using just numbers as the dropdown keys. It also lets me do things like:

if status < 100 then the record is current
if status > 100 then the record is archived

On improvements..
1. Make it so that dropdowns have no empty lines by default. Then, add an empty option in SugarFields code (with a translatable label "empty", "none" or something like that). Make sure that dropdowns with displayparam 'required' to TRUE cannot be submitted with that empty value.

2. Since Sugar's dropdowns are global, there are many in one place. A simple comment attribute would be welcome.

[veronicakatz]

I don't use non-standard characters as KEYS in dropdown lists, but it doesn't solve the problem.
For example: "Tecnico" (KEY) and "Técnico" (desired VALUE)
As soon as I edit the list in Studio, the VALUE gets wrong, though the KEY remains ok.