Content
View differences
Updated by Jan Sandbrink over 11 years ago
Disclaimer: I am not sure which of the steps are really neccessary for reproduction, so I’ll try to be specific. Probably more specific than neccessary.
### Reproduction
- setup instance with german and english locale (e.g. enterprise-dev)
- Set user language to german
- create a new custom field
- some title (change language of that to english)
- format: list
- some list entries (keep language as-is, should be german)
- save custom field
- call the API-endpoint for custom fields (e.g. https://enterprise-dev.qa.finn.de/api/v2/custom\_fields.json)
- either do not indicate language via HTTP or indicate english
### Expected
- The result contains my custom field
- my custom field has some `possible_values` set
### Actual
- The result contains my custom field
- there are no `possible_values` set
### Notes
- problem occurs when querying via .NET `WebRequest`
- querying the same URL with my browser gives me the german resource and thus contains `possible_values`
### Reproduction
- setup instance with german and english locale (e.g. enterprise-dev)
- Set user language to german
- create a new custom field
- some title (change language of that to english)
- format: list
- some list entries (keep language as-is, should be german)
- save custom field
- call the API-endpoint for custom fields (e.g. https://enterprise-dev.qa.finn.de/api/v2/custom\_fields.json)
- either do not indicate language via HTTP or indicate english
### Expected
- The result contains my custom field
- my custom field has some `possible_values` set
### Actual
- The result contains my custom field
- there are no `possible_values` set
### Notes
- problem occurs when querying via .NET `WebRequest`
- querying the same URL with my browser gives me the german resource and thus contains `possible_values`