Problem/Motivation

Some sites may need to keep the original update date and revision of the content because of legislations in the case when a user account was cancelled.

Steps to reproduce

-

Proposed resolution

Add a checkbox to the account settings page that will determinate if the user content will be sync or not.

Remaining tasks

The following two issues need to be merged first as dependencies:
#2809515: Simulate time passage instead of actually waiting in EntityTestMulChanged
#2329253: Allow ChangedItem to skip updating the entity's "changed" timestamp when synchronizing

User interface changes

Added a new checkbox under the "When cancelling a user account" radio boxes, where the user can decide if he wants to use this or not.

API changes

-

Data model changes

-

Release notes snippet

-

CommentFileSizeAuthor
#2 drupal-sync_content_on_cancel_account-3182786-2-9.2.patch5.45 KBgolddragon007

Comments

golddragon007 created an issue. See original summary.

golddragon007’s picture

golddragon007 commented
StatusFileSize
new drupal-sync_content_on_cancel_account-3182786-2-9.2.patch5.45 KB

This adds the checkbox, however, the patch from #2329253: Allow ChangedItem to skip updating the entity's "changed" timestamp when synchronizing needs to be used with it.

golddragon007’s picture

golddragon007 commented
Status: Active » Needs review

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs tests, +Needs subsystem maintainer review

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

Seems like an interesting idea.

Tagging for tests to show this new feature.
Tagging for subsystem maintainer review for their thoughts also.

Did not do a code review.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.