Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.i18n is broken with the current HEAD.
i had a look at it and indeed found that node.module has changed since latest i18n commit.
API changed, doc is here : http://drupal.org/node/22218
basically, i18n fails with node_list function undefined when trying to access the settings/i18n page.
i've tried to modify the code with directions given in the api doc above, but could not get the module work as it does on 4.6. settings works, but nodes are not assigned any translation upon creation, despite correct selection in the dropdown menu. translations can be created after initial creation.
My HEAD setup is not a fresh one, so i'll double check with a basic HEAD with i18n, using modifications done (changes for node_list & node_load functions), and let you know if i found something new.
i'm only 2 week old at drupal, so i'll try to help but i think drupal/i18n gurus should have a look :)
patch for simple modifications i've done is attached.
thanks for such a great module.
| Comment | File | Size | Author |
|---|---|---|---|
| i18n.test.patch | 1.73 KB | syllance |
Comments
Comment #1
syllance commentedCode to handle localized variables has gone from the i18n patches to includes/.inc files.
It also seems that node language is not handled correctly. Translations can be created but there is no default one upon creation, and when a translation is added, it's a new node without language that shows up.
Wanted to start my new project with 4.7, to get the new features and to contribute with testing, but I'll start it without i18n.
Would be glad to help, but I'm just starting with drupal and does not fully understand the drupal internals, at least to cope with module like i18n.
I'll continue to search for solution (getting back here if i can find one), and will take time to test patches if any.
thanks
Comment #2
syllance commentedSarting to look at a head forum issue (well, not issue, just lack of checks in head scripts :), I've started to look at the new node revisions introduced recently.
I think the i18n issues I'm facing might be related to this, so I'll investigate in order to add extra hours to my drupal knowledge :) Won't miss to post follow up if i can make the thing work.
however, i don't fully understand why localized variables support was removed from the patches. Is it a mistake or were they removed for a specific reason ?
thanks
Comment #3
jose reyero commentedWell, you're right in that the cvs version is not in sync with Drupal HEAD. We try to keep it up to date though, but Drupal HEAD is a moving target, so we'll have to wait till some Drupal 4.7 RC at least to have some usable code.
About language variables, they haven't been removed. It's only that I've found some workaround for not to require patching anymore :-)
Also, we've been focusing our efforts on some core patches, and hopefully the next 4.7 version of the module won't need any more patching, which I think is very good news.
Cheers,
Jose
Comment #4
syllance commentedThanks for your anwser. I've been reading more about the i18n project and realize that my post is useless with the target of hitting core, especially with the moving head target :)
i'm working with head for a project, making use of several *future* features, so i'm doing a lot of debugging work and try to give feedback to developpers when i can find fixes and make a patch. however, i now realize that i18n is definitely not a small module that can simply be upgraded to support latest code revision :) so sorry for the noise and early issue posting.
i'll follow latest updates and won't miss testing i18n when things will be usable, helping on smaller matters in the meantime :)
Comment #5
jose reyero commentedThe module upgrade is in progress. Please, follow up here: http://drupal.org/node/100431