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.
Example
You have a node that has been translated into other languages. Non-English translations are accessed using different domains, example.ca, example.au, etc. The task is to delete a translation and recreate it.
- Navigate to the node's Translate tab from the main domain, example.com.
- Click the down arrow in the Edit button for the language you want to delete.
- Right click "Delete" and open in a new tab.
- The confirmation page comes with the language domain, example.ca. Click the "Delete [LANGUAGE] translation" button.
- Significant time passes then the homepage is loaded, example.ca.
- Close the tab that was opened and refresh the Translate tab page.
- Then click to Add a translation for the language that was just deleted.
- The current window switches to example.ca with the "Create [LANGUAGE] translation of [NODE TITLE]" page.
- Scroll down and click "Save and keep published (this translation)" button.
- The page loads with a message:
Temporarily Unavailable The website that you're trying to reach is having technical difficulties and is currently unavailable. We are aware of the issue and are working hard to fix it. Thank you for your patience.
- At this point the node cannot be found in the example.com/admin/content page.
Comments
Comment #2
saurabh.tripathi.cs CreditAttribution: saurabh.tripathi.cs as a volunteer and at Faichi Solutions Pvt Ltd for Faichi Solutions Pvt Ltd commentedComment #3
saurabh.tripathi.cs CreditAttribution: saurabh.tripathi.cs as a volunteer and at Faichi Solutions Pvt Ltd for Faichi Solutions Pvt Ltd commentedI am still working on this, it seems that the language translation condition needs to be checked.
Comment #4
drupalninja99 CreditAttribution: drupalninja99 commented@saurabh.tripathi.cs this is a critical issue for our site. Is there a specific file/method we can look at to help research the issue?
Comment #5
saurabh.tripathi.cs CreditAttribution: saurabh.tripathi.cs as a volunteer and at Faichi Solutions Pvt Ltd for Faichi Solutions Pvt Ltd commentedhi drupalninja99 This issue https://www.drupal.org/node/2851029 seems to be related, though i have given the patch, but with the information stated by you above it seems we need to debug more.
Thanks
Comment #6
drupalninja99 CreditAttribution: drupalninja99 at Mediacurrent commentedHi @saurabh.tripathi.cs, thanks we can try. The critical issue is not just the error that April cited (which does happen sometimes), it's that the entire node is deleted when the editor only intended to delete the one translation. I am hoping that this patch might address that critical problem.
Comment #7
drupalninja99 CreditAttribution: drupalninja99 at Mediacurrent commentedAny updates on this?
Comment #8
DamienMcKennaI suggest detailing the steps to replicate the problem in a test.
Comment #9
saurabh.tripathi.cs CreditAttribution: saurabh.tripathi.cs as a volunteer and for Faichi Solutions Pvt Ltd commentedComment #13
larowlanAre you able to provide the stack-trace of the error that generates the message above?
I tested the steps above on simplytest.me with the Umami profile and could not yield the error.
The site I tested is here: https://master-hf2cbfmrnkazctjtdbelt1iafv6yxmcs.tugboat.qa/es/articles/d...
Thanks
Lee