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.

  1. Navigate to the node's Translate tab from the main domain, example.com.
  2. Click the down arrow in the Edit button for the language you want to delete.
  3. Right click "Delete" and open in a new tab.
  4. The confirmation page comes with the language domain, example.ca. Click the "Delete [LANGUAGE] translation" button.
  5. Significant time passes then the homepage is loaded, example.ca.
  6. Close the tab that was opened and refresh the Translate tab page.
  7. Then click to Add a translation for the language that was just deleted.
  8. The current window switches to example.ca with the "Create [LANGUAGE] translation of [NODE TITLE]" page.
  9. Scroll down and click "Save and keep published (this translation)" button.
  10. 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.
  11. At this point the node cannot be found in the example.com/admin/content page.

Comments

weekbeforenext created an issue. See original summary.

saurabh.tripathi.cs’s picture

Assigned: Unassigned » saurabh.tripathi.cs
saurabh.tripathi.cs’s picture

I am still working on this, it seems that the language translation condition needs to be checked.

drupalninja99’s picture

@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?

saurabh.tripathi.cs’s picture

hi 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

drupalninja99’s picture

Hi @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.

drupalninja99’s picture

Any updates on this?

DamienMcKenna’s picture

Issue tags: +Needs tests

I suggest detailing the steps to replicate the problem in a test.

saurabh.tripathi.cs’s picture

Assigned: saurabh.tripathi.cs » Unassigned

Version: 8.2.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
larowlan’s picture

Status: Active » Closed (cannot reproduce)
Issue tags: -translation, -Needs tests +Needs steps to reproduce, +Bug Smash Initiative

Are 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