- Issue created by @mark_fullmer
- Merge request !60Issue #3426185: Ability to set moderation state during cloning → (Merged) created by mark_fullmer
- Assigned to mark_fullmer
- last update
10 months ago 29 pass, 2 fail - Issue was unassigned.
- Status changed to Needs review
10 months ago 8:46pm 6 March 2024 - last update
10 months ago 30 pass - last update
10 months ago 30 pass - last update
10 months ago 30 pass - last update
10 months ago 30 pass - last update
10 months ago 30 pass - Status changed to RTBC
8 months ago 3:32pm 16 April 2024 - last update
8 months ago 30 pass - 🇫🇷France Grimreaper France 🇫🇷
Hi,
I am coming from #3384354-6: Error when cloning content type when content moderation is enabled → .
The MR fixes the bug and I think is a better long term solution than in the other issue.
Thanks a lot for the fix!
- Status changed to Fixed
8 months ago 9:57am 17 April 2024 - 🇮🇳India rajeshreeputra Pune
This solution is awesome thanks @markfullmer for fixing and @Grimreaper for testing.
- last update
8 months ago 30 pass -
Rajeshreeputra →
committed 01499733 on 2.x authored by
mark_fullmer →
Issue #3426185 by mark_fullmer, Grimreaper, Rajeshreeputra: Ability to...
-
Rajeshreeputra →
committed 01499733 on 2.x authored by
mark_fullmer →
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India Supreetam09 Kolkata
This is causing inconsistent behaviour in multilingual sites.
In a multilingual site, the moderation status dropdown is not shown in the entity clone form, rather the oldSave cloned Content as publishedcheckbox is shown.
But when we select the checkbox and clone the entity, the entity gets cloned in draft state, instead of published as selected - this behaviour is inconsistent.First point in Acceptance Criteria says,
If multiple languages are configured on the site, there is no change to the entity clone form (this preserves existing behavior that will set all cloned translations to "draft")
But, if thats the case, either we need to hide the Published checkbox completely for multilingual sites, or be consistent with chosen option and publish all translations upon cloning.
- Merge request !85Issue #3426185: Handle cloning as Published for multilingual sites. → (Open) created by Supreetam09
- 🇮🇳India Supreetam09 Kolkata
Created new MR https://git.drupalcode.org/project/entity_clone/-/merge_requests/85 to handle the issue
Request to maintainer to reopen this and set to needs review. - 🇮🇳India rajeshreeputra Pune
I think in this case we should hide the Published checkbox in multilingual case to preserves existing behavior that will set all cloned translations to "draft".
Instead of working on this issue and we create new 2 issues:
- For hiding Published checkbox in multilingual case and set all cloned translations to "draft".
- For showing Published checkbox in multilingual case and publish all translations upon cloning.
Or we can create single issue with Published checkbox and checkbox to set all translation published.
@Supreetam09, what is you take on this?
- 🇮🇳India Supreetam09 Kolkata
@Rajeshreeputra I am fine with taking it up in a separate issue as well, ultimately resolving the issue matters.
(I think it would be better to keep both issues 1 & 2 under one umbrella for better context, so creating a single issue would be better)