search

enonic / app-contentstudio

Content Studio of Enonic XP
GNU General Public License v3.0
10 stars 4 forks source link

Duplicated content should always be created in state "In Progress" #1382

Closed Sneiwert closed 3 years ago

Sneiwert commented 5 years ago

When copying an event it shows "ready to publish", but nothing has been edited or approved.

Sneiwert commented 5 years ago

Screenshot 2019-09-17 at 13 04 49

alansemenov commented 5 years ago

@Sneiwert It's not obvious to me that this is wrong behaviour. When you duplicate a content that is "ready", the duplicate is also "ready". When you start changing the duplicate - which is what you most likely duplicated it for - then it will change to "In progress". Makes total sense to me.

Let's discuss this.

Sneiwert commented 5 years ago

I see what you mean. But when the duplicate has an old event date from the past, it should automatically detect that this content has to be modified before being published. The copied content should be validated before it is showing "Ready".

Sneiwert commented 5 years ago

I talked to @sigdestad about this, he knows the issue.

alansemenov commented 3 years ago

Should most likely be fixed in admin API.

ashklianko commented 3 years ago

@alansemenov we only send ids to duplicate, result is fully created on backend, so I believe it is a backend task

alansemenov commented 3 years ago

Issue moved to enonic/xp #8829 via ZenHub