New version is created every time you click "Publish" button

This issue has been resolved in LPS-28886.

My mistake I confused this with Doclib issue but this isn't implemented in web content.

Hey Jorge,

Can we implement similar versioning strategy to web content as we did with D&M on LPS-28886?

I think that the issue is probably not entirely clear. The reason why it says modified is because the new version is created if any modification is done and saved. Even if you don't publish and saved as draft.

Possible alternative messages would be:
"A new version will be created automatically if this content is modified and saved."
"A new version will be created automatically if this content is saved as draft or published."

BTW, Mika I really don't find any relationship between LPS-28886 and this ticket.

Jorge, the relation is that in doclib we used to create a new version every time you checked in a document even if there we no changes (we also retained the old behavior with property so you could set the versioning policy). So what's suggested here is to implement similar functionality for web content. Now granted web content doesn't have the same check out / check in as documents.

I see. Yeah, I don't think that applies here because there is no concept of checkin, checkout.

I'm going to close this as won't fix since I'm not convinced any of my suggested messages are better than the current one.

Szymon, since you are the one who got confused with the current message, if you can propose an alternative message it would be appreciated. If you do so I'll reopen or create another ticket to improve it.

Checking in and out is a very good thing especially in companies with lots of Editors. But that's a big work. As we analyse this issue we came to conclusion that there is no easy way to compare versions of web content especially when it has complicated structure. So I propose to go with solution #2 which is "remove that confusing message".

Hi Szymon,

Thanks for answering.

I would prefer to not just remove the message from this portlet. If anything it would be to be removed from all other places in which it is being shown (Doc Lib, Wiki, Web Content and also when creating a page revision).

We added this message so that it was clear for users that they could safely make modifications to the content because a new version would be created and the current one (which is published) will be saved as an old version. That only happens for content types that have versioning, but for example not for Blogs. Considering this, do you still think we should remove that message?

Hi Jorge,

I think that users don't need to be informed about every little functionality of Liferay (or any other CMS) system. It's more "if you are using it, you should know what it can do" approach that keeps everything simple and clear. Prepare good user guide and self-explanatory user interface and such messages will be obsolote.

I also did quick research to check how does it look like in other CMS systems with content versioning or content status (draft/approved). Well, they don't show such messages.

That is why I think we should remove that message from web content edition page and from all other places in which it is being shown.

That's a good point. I'll run it through product management and unless there are any issue I'll make the change.