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.
-
Add a checkbox to the account settings page that will determinate if the user content will be sync or not.
The following two issues need to be merged first as dependencies:
📌
Simulate time passage instead of actually waiting in EntityTestMulChanged
Needs work
📌
Allow ChangedItem to skip updating the entity's "changed" timestamp when synchronizing
Fixed
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.
-
-
-
Needs work
10.1 ✨
Last updated
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
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.