Modifying option group values in 4.5+

[sdragnev]

I just noticed that if I click on Edit next to an option group value in civi 4.5, I seem to no longer be able to change it.

I couldn't find anything in the issue tracker, but was this changed on purpose to avoid data integrity issues? Is there a way to turn it back on?

Thanks.

[Coleman Watts]

As you can see in the public demo site (always a good reference) option values can still be changed by clicking on the wrench icon next to them.

Can you post a more detailed description of the problem? Where exactly is it failing? Can you open up your browser's console (F12) and report on any red error messages you see when you try to edit options?

PS Can you update your CiviCRM version in your forum profile?

[sdragnev]

Thanks for the quick reply.
Maybe I'm looking at the wrong place?

Here's a screenshot of the event type option values (as an example).
http://i.imgur.com/hCL1nhG.png

If I click edit next to Conference, there is no option to change the value. Just label, description and weight.
http://i.imgur.com/Nsx8Wrc.png

I understand why the ability to change the value can be issue so I would not be surprised if it's no longer supported. Problem is, we're using custom ones to store some values that should be modifiable.

PS I am using 4.4 right now. Was checking out the master branch which is where I saw this issue so I checked 4.5 as well.

[Coleman Watts]

Ok I understand your issue now. The screenshots help, thanks.
But I can't understand why you would want to change the value of an event type in the db. Seems like it would result in data-integrity issues. Besides those values are just serial (1, 2, 3, 4 and so on).
If you really want to do it, use phpMyAdmin but be sure you update all references to it as well.

[sdragnev]

I was just using event type as an example from demo site, but yeah. Thanks.

[JoeMurray]

We have not been using 'value' as a synonym for machine 'name' for option values. Instead, we have worked around the problem of not having a machine name by using the label as the machine name. I think it would be more appropriate to add a name field rather than make value non-editable. For our purposes, we have used the value field as the value in various key-value pairs.