Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Editing translations wrong redirect:
This bug can be reproduced on simplytest.me as shown in the attachment. When using Seven this cannot be reproduced so it's not a Drupal Core fault.
Thanks.
Comment | File | Size | Author |
---|---|---|---|
#9 | 2868100-9.patch | 742 bytes | nielsvandermolen |
#4 | Screen Shot 2018-01-15 at 12.54.47 PM.png | 83.92 KB | sriman |
bootstrap.mp4 | 6.03 MB | gge | |
en.png | 111.14 KB | gge | |
es.png | 106.57 KB | gge |
Comments
Comment #2
markhalliwellComment #3
sriman CreditAttribution: sriman as a volunteer commented@markcarver
Even after applying the patch the issue is not resolved.
Comment #4
sriman CreditAttribution: sriman as a volunteer commented@markcarver
Issue is not resolved even after applying the patch
Comment #5
sriman CreditAttribution: sriman as a volunteer commentedApplied the patch given by markcarver & removed the below if condition in the BootstrapDropdown.php it works like a charm.
to
Comment #6
gge CreditAttribution: gge commentedUnfortunately I have to re-open this. Just checked 8.x-3.x-dev (released on 12 Feb 2018), the bug is still there as @sriman reported and #2901106: Multilingual dropbutton links do not contain correct language identifier didn't solve this issue. @sriman's advice works but doesn't seem to be the right solution as @markcarver commented here.
Comment #7
markhalliwellNo one has given an explanation as to why unwrapping supposedly "works". If the language option was already set (by a module), the theme shouldn't be overriding it...
Comment #8
gge CreditAttribution: gge commentedI have no idea why it works.
One more thing just noticed: if thatif
statement is removed the behavior explained here #2939166: Clicking "edit" dropdown button navigates to incorrect content is also fixed.Now I don't know what other problems could appear if
if (empty($element['url']->getOption('language')))
is removed.OOOps sorry! Huge mistake! Sorry!
Comment #9
nielsvandermolen CreditAttribution: nielsvandermolen at Open Social for Open Social commentedAdding the patch of #5 for Bootstrap 3.9 currently in use in Open Social. I am not sure if this is a core issue but I have verified that the same issue does not happen on Drupal core themes.
Comment #10
MaskOta CreditAttribution: MaskOta commentedThis problem still exists. Maybe the solution is not correct but the issue very much exists.
Setting to active so that the comunity is aware and maybe someone can spot the problem
Comment #11
markhalliwellSee #7. Postponed issues are not closed issues, they show up in normal (open) issue queue lists.
Comment #12
leisurman CreditAttribution: leisurman commentedI am having the same translation wrong url issue. This patch fails to apply using Composer. https://www.drupal.org/project/bootstrap/issues/2901106#comment-12419030. The patch here on this page (#9) applies and works. https://www.drupal.org/project/bootstrap/issues/2868100#comment-12565115
Comment #13
KingdutchI'm unable to figure out where this happens but it does appear that the language for the URL is already set somewhere and does not correspond to the link itself.
I've tested this on SImplytest.me with Bootstrap 3.19 to ensure that it's no other module or theme that's interfering. When I use Bootstrap then when I try to edit the English translation of a node from /node/*/translations while viewing this overview in a non-English language (e.g. Dutch) then I will end up editing the non-english translation. This also works the other way around.
Simply using the Seven theme for this overview does not have this problem. This suggests that this error is introduced elsewhere in Bootstrap (or not fixed in Bootstrap) but I can not find it.
Comment #14
markhalliwellSaying "I don't know" doesn't warrant a status change as no new information has been presented on why it was postponed in the first place.
Comment #15
markhalliwellI'm going to go ahead and commit the patch from #9. I'd really like to know why this is or isn't working the way it is intended, but I've expanded the @todo to mention this issue so we can revisit this at another time.