Closed (outdated)
Project:
Drupal core
Version:
6.x-dev
Component:
language system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 May 2010 at 10:08 UTC
Updated:
2 Mar 2016 at 22:18 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jose reyero commentedThis is not handled by i18n. You can reopen the issue for Drupal core.
Comment #2
mrfelton commentedComment #3
mrfelton commentedAttached patch seems to resolve this.
Comment #4
rolodmonkey commentedComment #5
chaugi commented#3 resolves an issue, why this is still not included in Drupal 6.20?!
Comment #6
rolodmonkey commentedchaugi,
There is a set procedure for getting a patch committed to the core. Even if a patch fixes a problem, it needs to be reviewed to make sure that it doesn't break something else.
First, the patch needs to be re-submitted in order to go through automated testing. I would do this myself, but the last time I tried, I had a lot of problems with that part of the system: http://drupal.org/node/357021#comment-3666750
After that, the patch still needs to be reviewed by other members of the community. If it looks okay, they can change the status to 'Ready to be committed'. Only then, will the patch be available to roll into the next release.
I can understand your frustration, but this process is necessary. You would be surprised how often a patch that looks really simple breaks something else that no-one thought about.
Comment #7
chaugi commentedRoloDMonkey
Thank you very much for your kind explanation!
Comment #8
loparr commentedHi, your patch resolves this issue but only for the first time. After you go back to your translated node and edit it, there is no teaser again. What can be done here?
Thank you
Comment #9
VolkerLanz commentedThere are two orthogonal issues here that need attention.
The first is that a newly created page translation does not have the teaser preset with the original language's version. This is a small glitch that is indeed fixed by the patch provided above.
The second, much graver issue is that if you uncheck "Show summary in full view" in a translated page the teaser will only be saved once and be lost after the first (and each subsequent) update.
I've tracked this issue down to the translation management modules, namely to the nodeapi implementation in the icl_content module. Disabling _all_ translation management modules (each of them will register the icl_content hook, apparently) fixes the behaviour for me.
Of course disabling all those modules will also make the translation management features basically nonexistant.
Comment #10
loparr commentedHi,
The lost summary is quite annoying because it seems there is no way to put the teaser back. The only option was to create a new node etc... Before someone skilled would post a patch, I would just reenter the missing summary into database.
Comment #11
noup commentedSubscribing.