- Issue created by @artis.bajars
- π±π»Latvia artis.bajars
Had some time to look at this closer and it seems to me that all that's needed to prevent the
uri
from jumping from theentity:
to theinternal:
schema is to try and load the entity translation from context. Please review. - Status changed to Needs review
over 1 year ago 12:18pm 21 April 2023 - last update
over 1 year ago 83 pass - last update
11 months ago Patch Failed to Apply - π¨πSwitzerland berdir Switzerland
Was running into related issues as well, something changed with a recent release.
I also had to change \Drupal\linkit\Plugin\Field\FieldFormatter\LinkitFormatter::getSubstitutedUrl(), which has very similar code. This mirrors \Drupal\linkit\Utility\LinkitHelper::getEntityFromUserInput(), which is called when the link options are not present (so possibly that's the change, having those vs not).
- last update
11 months ago Patch Failed to Apply - last update
11 months ago Patch Failed to Apply - π¨πSwitzerland berdir Switzerland
Meh, looks like this was already addressed in π Direct URL to media file entity does not work because relative URL does not pass URL path validation Fixed based on my review IIRC. I'm getting old :)
- Status changed to Postponed: needs info
3 months ago 11:42am 6 September 2024 - π¨πSwitzerland berdir Switzerland
We finally got around to doing a bit more testing on this.
We also see that editing then shows the URL including the alias, and that is weird, but I don't think there's anything special about multilingual here, it also does that on the default language.
What we can no longer reproduce, with the formatter change from the other issue, is that the link in the frontend is broken. We saved the translation with the URL including language prefix, and then changed the alias of the target node and that alias was immediately updated and displayed correctly in the linkit field.
I'd suggest to close this, Ithink there are other option issues around inconsistent display with/without alias when adding/editing content.