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.Hi all and thanks for your work on this module.
I can see lots of efforts are invested, but I can't the hell find out how to use this module.
Could somebody give me a basic workflow for translating, say, just one field data on a basic content type ?
I enabled the module and I use i18n to translate most of the content, but I need to implement something special to translate profile2 data.
As of now, I activated the 'node' and 'profile' types on the admin page, and the field settings say 'Users may translate this field', but I was unable to find where the real translating stuff lies.
I tried some sample data and checked in the translation strings (like anything which goes through t() ), but I can't find any of mines.
I know my question is a bit dumb compared to the complex development problems going on here, but I would be happy to give feedback if I could at least understand the basic concepts.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | et-1109198-7.patch | 2.62 KB | plach |
| #2 | entity_translation.jpg | 273.96 KB | Countzero |
Comments
Comment #1
plachHi, we are aware that getting up and running with ET is not exactly simple, we have an open issue trying to address this: #1030038: Initial setup lacks UX.
You might be interested in testing/reviewing the patch, anyway you will find most (if not all) of the answers you need over there.
Comment #2
Countzero CreditAttribution: Countzero commentedAlready read this thread, will do it again.
I tested a bit further and found that the 'Translate' tab seems to make i18n go crazy (see attached screenshot).
The same tab works perfectly with Entity Translation disabled.
I didn't find anything about this in the issue queue.
Comment #3
Countzero CreditAttribution: Countzero commentedI applied the patch (then module clean uninstall and cache clearing, then reenabled) but it didn't change anything except for the help messages, which are welcome anyway.
I'm turning this into a bug report, as it renders the other translation modules unusable.
Correct me if I'm wrong.
Comment #4
plachRetitling.
Yes, the patch only provides those help messages :)
Probably what we need is a Help text or a documentation page.
Comment #5
plachComment #6
Countzero CreditAttribution: Countzero commentedIt seems to be only a matter of incompatible paths.
I tried to prefix all the hook_menu entries (replacing translate with enttranslate) and relevant links in the code and the modules seem to live together without trouble.
Deciding which paths the module should use is way above me, but maybe it would be a good idea just to change this fast so people like me could make some more testing and give feedback ?
Comment #7
plachThe attached patch should fix the issue.
Comment #8
Countzero CreditAttribution: Countzero commentedYes, the patch seems to resolve the issue : one content type with 'Enabled, with translation' and another with 'Enabled, with Entity translation' both seem to react cleanly.
I just got a message saying :
... but I guess it's unrelated.
Thanks for this fix (one of the quickest I ever got on d.o I guess).
Now back to trying to integrate the thing with profile2. If you have any hint ... or perhaps should I open a new issue ?
Comment #9
plachThe other issue has already been reported: #1096028: Notice : Undefined index: href dans entity_translation_overview() (ligne 114 dans entity_translation.admin.inc)..
Comment #10
plachCommitted to HEAD.
Comment #12
BenK CreditAttribution: BenK commentedJust keeping track of this thread.