- Issue created by @tonyhrx
- First commit to issue fork.
- 🇺🇦Ukraine yakim
I’ve investigated this issue but was unable to reproduce it using the latest stable versions of Drupal and CiviCRM.
Here’s what I did to test:
Enabled and configured the modules: `content_translation`, `locale`, and `language`.
Create a new Webform instance, and check the "Enable CiviCRM Processing" option.
Added the “Gender” field via the CiviCRM contact element (Options Select List).
Added a custom gender option and translated it using the Webform’s “Translate” tab.As shown in the attached screenshot, all options are displayed correctly and are fully selectable. The translations also appear to work as expected.
Environment details:
- Drupal: 10.4.8
- PHP: 8.3.21
- MariaDB: 10.11.11
- Web server: nginx/1.28.0
- Local stack: DDEV
- Webform CiviCRM Integration: 6.3.0
@tonyhrx, could you please clarify the exact steps required to reproduce the issue? It would be especially helpful to know:
- The versions of CiviCRM and Webform you’re using.
- Which specific part isn’t working as expected: option translation display, form submission, or value mapping?Happy to test again once I have more information!