Thank you for bringing this to my attention. Iโll fix it soon.
I installed Drupal 10.3.10 and uninstalled the Locale and Language modules (core modules). After that, I created a few Article nodes. Later, I added a new Taxonomy reference field to the Article content type.
However, when trying to edit an article and add a value to the taxonomy reference field, I encountered the following error:
The value you selected is not a valid choice.
harivenuv โ made their first commit to this issueโs fork.
harivenuv โ made their first commit to this issueโs fork.
Upgrade compatibility to Drupal 11
This commit ensures compatibility with Drupal 11 by updating codebase dependencies and addressing deprecated functionalities. Thoroughly tested for seamless integration with Drupal 11 core.
harivenuv โ made their first commit to this issueโs fork.
Thanks you for the effort
Sure, I will provide an update on this
Hi @tgoeg
Thank you for raising this concern. I understand that pulling the player JS from an external source like https://unpkg.com might not be suitable for all users due to data protection and performance considerations.
To address this, I have already moved the file to a local path. Here's the updated configuration for the lottiefiles library
This ensures that the file is served locally, improving performance and addressing potential data privacy concerns. Please let me know if you have any additional feedback or suggestions.
Thank you @sourabhsisodia_ @guido_s
Patch: Extract the first IP address from comma-separated `HTTP_X_FORWARDED_FOR` header
- Updated the Reverse Proxy Header module to properly handle multiple IP addresses in the `HTTP_X_FORWARDED_FOR` header.
- The module now extracts and uses the first IP address from a comma-separated list.
- Ensures that only the first non-private, non-reserved IP address is used, improving compatibility with multiple proxy setups.
- Fixes potential issues where the module could incorrectly handle multiple forwarded IP addresses, leading to incorrect client IP detection.
Fixed
Added field update hook, Please do a configuration export after this update.
Hi @lluisandreu,
Not able to reproduce this bug in my environment.
First of all i'm not using this module, but i faced the same issue. This issue due to the user object not loaded correctly on the form, possibly due to a missing of user ID from the route used in your form. This problem often arises in Ajax callbacks button, where the route name and user parameter should be passed through the Ajax's URL property.
'#ajax' => [
'callback' => 'custom_user__back_to_step_2',
'url' => Url::fromRoute('custom_user.user_edit', ['user' => $user->id()]),
'options' => [
'query' => [
FormBuilderInterface::AJAX_FORM_REQUEST => TRUE,
],
],
],
Hey, any solution for this ?
Hey yash_khandelwal ,
You patch not working to default branch. I'm making some amendment on that for merging, thank you for your support.
Thank you @dtamajon
Hey alemadlei,
Thank you for contacting us :)
as of now the D10 migration already covered on this project, do you have any new idea to add-on to this project ?
Thank you for the patch
harivenuv โ changed the visibility of the branch 3401975-Re-ensure-the-file-upload to hidden.
harivenuv โ made their first commit to this issueโs fork.
Patch not working
`data-dark-mode-switch` attribute not rendering in DOM due to that the JS throwing error, Tested in Drupal 10.2
Yes, not working for me too, patch should be merged. Really stuck here drupal-lenient not helped
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/twig_extensions 2.x-dev@dev -> satisfiable by drupal/twig_extensions[2.x-dev (alias of dev-2.x)].
- drupal/core-recommended 10.2.0-beta1 requires drupal/core 10.2.0-beta1 -> satisfiable by drupal/core[10.2.0-beta1].
- Conclusion: don't install drupal/core 10.2.0-beta1 (conflict analysis result)
- drupal/core-recommended 10.2.0-rc1 requires drupal/core 10.2.0-rc1 -> satisfiable by drupal/core[10.2.0-rc1].
- Conclusion: don't install drupal/core 10.2.0-rc1 (conflict analysis result)
- drupal/core-recommended[10.1.7, ..., 10.1.x-dev] require twig/twig ~v3.6.0 -> satisfiable by twig/twig[v3.6.0, v3.6.1].
- Conclusion: don't install twig/twig v3.6.1 (conflict analysis result)
- drupal/core-recommended 10.2.0-alpha1 requires twig/twig ~v3.7.1 -> satisfiable by twig/twig[v3.7.1].
- Conclusion: don't install twig/twig v3.7.1 (conflict analysis result)
- drupal/core 10.2.x-dev conflicts with drush/drush <12.4.3.
- drupal/core-recommended 10.2.x-dev requires drupal/core 10.2.x-dev -> satisfiable by drupal/core[10.2.x-dev].
- Root composer.json requires drupal/core-recommended ^10.1.7 -> satisfiable by drupal/core-recommended[10.1.7, ..., 10.2.x-dev].
- Root composer.json requires drush/drush ^11.0 -> satisfiable by drush/drush[11.0.0-rc1, ..., 11.x-dev].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Composer [update] failed, composer command failed: exit status 2. stderr=
Hi @pbone3b, there is a problem, your patch will help us with people with fresh installation. what happen people already using this module ?
#2 patch not work with version 8.x-1.2
Create a useful patch, which may help developer who trying to upgrade to D10
Thank you for reporting this @Daniel, this was i expected, it might be little hard to do this on udpate hook. Meanwhile i'm checking solution for this.
Thank you @dineshkumarbollu @tanuja-bohra
harivenuv โ made their first commit to this issueโs fork.
Hi @mangollove,
Please share your resolution steps, that can be help the community
I'm facing the same issue, version 11.9.4
I'm also facing same issue.
Hi @afeijo,
Thanks you for the wonderful idea, we can do that.
Hi @Chris Dart,
Thanks you for the patch, will review and merge
Hi @dtamajon,
Thanks you for patch, will review and merge.
Hi @dtamajon,
Thanks you for the patch, will review and merge
Thanks sivakarthik229, added you as maintainer