I'd say this issue is still valid as the dropdown menu is still very user unfriendly, when scrolling the languages.
Greetings!
This problem is still apparent in the latest version for the Paragraphs module, 1.16. Here is the updated version of the patch.
Greetings,
I was studying the issue and tried the patch on our Drupal project's Sitemap, and it didn't provide the desired result to remove the language prefix. The core version in the project in which I'm working is 10.1.2 and the module version is 4.1.x. I was studying the core issue to this and found a similar issue on OpenID Connect / OAuth client module's issue https://www.drupal.org/project/openid_connect/issues/3383036 ✨ Redirect URI has the language prefix in it (in D10) Needs review / Redirect URI has the language prefix in it (in D10).
In this patch, the language for the URL is disabled, replacing it with `path_processing` set to false. And the same solution is proposed on the patch I'm providing with this comment on the issue, also with an interdiff to the prior patch.
What is the status of this issue? Would like to see this merged so that our project can move forward on Drupal 10 update.
+1 (Waiting for the D10 compatible release)
In this, I will upload the interdiff between versions #83 and #85. To answer #86, it appears it's not possible to edit an old comment and provide a file with it, so I will be uploading the interdiff file in this comment.
All right, as stated in #84, these should be fixed with the version provided in this comment, #85.
I had some issues in #74 on the project for which I'm working on. The code section where all the available string translation contexts are fetched in the function translateFilters() didn't apply.
This is an updated version of the patch where the said code segment is placed between the filters array and language fetching sans English.
Greetings!
I tested this on my local installation for a Drupal 9 site. The patch applied successfully and I have thus updated the status from Needs review to Reviewed & tested by the community.
As mErilainen stated above, there really was some deprecated code in the aforementioned classes SearchLinks.php and ExtraLinks.php.
In this, the change for adding the missing accessCheck is included as well as the interdiff file between the original patch and the newer patch.
The latest patch, which is generated with U1 argument used in git diff for *.info.yml files.
There were some deprecated code, invalid composer.jsoon and info.yml version for the drupal/core.
In this patch, an accessCheck is added to entity queries, as is the correct core version required for composer.json and module.info.yml.
This patch should fix the compatibility issues along with the deprecated function calls. Checked with module.
This is the conclusive patch for the D10 compatibility, with all the changes requested on the code by the module!
Tested this patch for the link_description and reviewed the changes. Looks good to me!
And this patch has the fixed, along with the .
This patch should have the correct versions for the core_version_requirement.
The fix is quite simple, only needs an update to the module's -file.
jheinon_finland → created an issue.
How can I create an issue on updating a Drupal module, if it needs to be a confirmed user? There are some contrib modules without the Drupal 10 compatibility in my project, with no issues created on them that needs working.
jheinon_finland → created an issue.