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.
I'm using the latest dev version of the module. Should I add more details?
Comment | File | Size | Author |
---|---|---|---|
#12 | tmgmt-1976588-12.patch | 1.26 KB | jfhovinne |
| |||
#11 | tmgmt_node.patch | 788 bytes | sri@re |
#9 | tmgmt-remove-pid-entity-1976588-9-7.x.patch | 651 bytes | mgalalm |
Comments
Comment #1
merdekiti CreditAttribution: merdekiti commentedAny update here?
Comment #2
BerdirThis is also not OHT specific. Anything that happens after accepting before a job is submitted and after a job item was accepted (or while accepting it) is TMGMT core. It's only translator specific if there's a problem with the submitted information but it shows up correctly on the job item or if the sent translation is wrong or missing.
Again, need more information here. We recently fixed a pathauto related alias bug for entity translation, make sure you're using the latest version of all related modules (tmgmt, entity_translation, pathauto).
Provide detailed steps to reproduce if the error still happens.
Comment #3
AusJohn CreditAttribution: AusJohn commentedThis is the same issue I'm currently having. Might be anyway..
Using multilingual urls (pathauto)
Using content translation (not fields).
Create an article and publish it.
The aliased url is created automagically.
The aliased url for the original works: site.com/cute-dog
Create a Translation Job.
User translates article and saves.
Editor checks accuracy and clicks 'complete job'.
Original article URL is reverted to: site.com/node/12
Translated article URL works fine: site.com/ja/可愛い犬
Right after saving the job as completed. The message states "The translation for HYPERLINK has been accepted"
The hyperlink has already changed to node/12 at that point.
The aliased url is derived from the node title. If I translate the article directly (not using tmgmt), the original articles path is not affected.
Not sure what is causing this.
Comment #4
AusJohn CreditAttribution: AusJohn commentedComment #5
AusJohn CreditAttribution: AusJohn commentedIf I open the original node after translation job complete, the alias is gone. Deleted.
I hit save with automatic generation ticked, the alias is fixed and everything works. I'll have another look later but, I'm no expert in finding the cause of these things.
I know something is deleting the alias of original/translated versions. To re-apply these aliases, one must open and again save the original/other translated nodes. Not exactly user friendly.
Comment #6
ippey CreditAttribution: ippey as a volunteer and at ANNAI commentedI got the same issue.
It was occurred when I installed "TMGMT" and "workbench_moderation" on Drupal7.
but it was not occurred when I installed only "TMGMT" on Drupal7.
"workbench_moderation" has a method "workbench_moderation_node_load",
this method gets url_alias data.
I think I was able to solve this issue.
Please make sure of the following attachment file.
Best regards.
Comment #7
mgalalm CreditAttribution: mgalalm at Johnson & Johnson commentedThis is ippey's fix version for entity
Comment #8
mgalalm CreditAttribution: mgalalm at Johnson & Johnson commentedComment #9
mgalalm CreditAttribution: mgalalm at Johnson & Johnson commentedComment #10
sri@re CreditAttribution: sri@re commentedits working.can anyone please test.
Comment #11
sri@re CreditAttribution: sri@re commentedComment #12
jfhovinne CreditAttribution: jfhovinne commented