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.It might be related to: http://drupal.org/node/1237266
I was using I18N_MODE_LOCALIZE mode, and found that the menus, the vocabulary lists and the termlists are not translated.
It did not help me when I changed to I18N_MODE_TRANSLATE.
I am working on a patch. It is working, but I am not sure it is the best solution.
I have copied the taxonomy_overview_terms() and the vocabulary_overview_terms from core taxonomy module, and added some translation code. (With these functions come the ..._submit() and theme_...() functions too.)
Now I am thinking whether I should make it in the hook_form_alter call?
I am a beginner programmer, and I don't want to make a mess. I also need time before I can use preprocess, haven't even tried it.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | translate_vocabulary_menu-1397078-1.patch | 826 bytes | balagan |
| #4 | translate_taxonomy-termlist-1397078-2.patch | 1.72 KB | balagan |
| #4 | termlist_submit-1397078-3.patch | 5.68 KB | balagan |
| #4 | translate_vocabulary_list-1397078-4.patch | 954 bytes | balagan |
| #4 | vocabulary_submit-1397078-5.patch | 1.31 KB | balagan |
Comments
Comment #1
balagan CreditAttribution: balagan commentedI went by the hook_form_alter calls. For me it is working with LOCALIZE mode, haven't checked with TRANSLATE.
Comment #2
balagan CreditAttribution: balagan commentedForget it, now I have found the proper hooks to use, still working on it.
Comment #3
balagan CreditAttribution: balagan commentedI wanted to go another way, with hook_taxonomy_vocabulary_presave, but for me it seems impossible.
Anyway, I got some feedback that my patch is too big to review, so I broke it up into 5 parts.
Comment #4
balagan CreditAttribution: balagan commentedI have deleted unnecessary whitespace from the patches, and fixed a bug in the last one. Now these should really work. Sorry, for messing up this thread.
Comment #5
Jose Reyero CreditAttribution: Jose Reyero commentedThe idea looks good, though massively replacing Drupal core pages may not be a 'sustainable strategy'. We need to be aware that there may be other modules adding their stuff in there and this way we are breaking all of them.
So I think we should take a more 'lightweight' approach and try to either page_alter() or form_alter() specific elements for specific pages instead.
About the patch, maybe we should go for some of the parts first (menus?) and then once we get it fixed, we use the same strategy to fix the others. That should save you some time updating patches.
Comment #6
balagan CreditAttribution: balagan commentedComment #8
Jose Reyero CreditAttribution: Jose Reyero commentedA lots of things have changed in this module, this may not apply, or some parts may not be needed anymore. Besides, this seems not to be worked on anymore (for almost a year).
So I'm closing this one -thanks for the work though-. Feel free to reopen if you want to update and keep working on the patch.
Comment #8.0
Jose Reyero CreditAttribution: Jose Reyero commentedTrying to hide my ignorance :)