The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Website uses field entity translation to serve Czech (the default) and English language content. When editing node content, the CKEditor Link module saves internal links in the format /node/[nid] and is rendering them in a fully aliased, language-prefixed format - but only in one language (Czech), regardless of the currently selected language.
Current environment:
- CKEditor Link 7.x-2.2
- CKEditor 3.5.2.6450
- Wysiwyg 7.x-2.1
- Drupal 7.14
I've tried moving the CKEditor Link Filter to the top and bottom of the list of text format filters, but did not see any change in behavior. Even after switching the default site language to English, the URLs were still always rendered with the Czech prefix and alias.
Content language detection is currently set to first check the interface language (determined by URL path prefix) and then by URL path prefix, though I've tried having content detection set to URL first and had the same results. Switching languages using the 'Language switcher (Content)' block displays the correct translated content; only the internal path URLs formatted by CKEditor Link filter do not change.
I've run out of ideas of what to try next and hadn't seen a similar issue reported. I've followed all the steps outlined in the README. Hopefully it is a configuration step I missed rather than a bug, but I'm not seeing it. Any suggestions would be greatly appreciated. Thanks for your help.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | ignore_node_language-1628954-6.patch | 665 bytes | anrikun |
Comments
Comment #1
anrikun commentedCan you send me a link to your site? If so, use my contact form (do not post it here).
Is there a way I could access your site as an admin?
Comment #2
wnicklin commentedThanks for the fast reply. I will set up an account for you and a link to the site.
Comment #3
wnicklin commentedChanging status to feature request - CKEditor Link doesn't support the entity translation module at this time.
Comment #4
anrikun commented@wnicklin: read my last mail. Could you try what I wrote?Comment #5
anrikun commented@wnicklin:
The problem is that Entity translation translates fields, not nodes, but still set a language (non-UND) to the node itself.
IMHO, this does not make sense. Entity translation should leave node (core database field) language to UND and keep track of the source language of node fields in a separated database field.
As Entity translation is still in an alpha stage, I suggest you post an issue about this in the Entity translation issue queue.
I'm marking this issue as "won't fix" for now. Feel free to reopen if you get more information.
Comment #6
anrikun commented@wnicklin:
In the meantime, use this patch. It should fix your problem.
Comment #7
wnicklin commented@anrikun:
The patch solved the problem for me.
I'll follow up on the entity translation issue queue if anything further is needed.
Thanks again for all your help. Great module.
Comment #8
tumesch commentedI was hit by the same incompatibility with Entity Translation, meanwhile at version 7.x-1.0-beta2.
My case: German site, prefix 'en' for English pages. Could not get English internal links to work with translated fields. After the above patch everything plays nicely.
As the Entity Translation module will be increasingly prevalent - it is already part of D8 core, I reopen this feature request.
@anrikun: Could you implement this patch as configuration item?
Thanks for all your work!
Comment #9
anrikun commented@tumesch: actually, this is now a duplicate of #1875720: Support nodes translated with Entity Translation that provides a patch to review.