I wouldn't necessarily call this a bug. When you create a new article, you can input your own creation time and if that is empty then the current time is used. If any time should be adjusted during the copy process, it should be the modified time (as it was newly updated), otherwise the create/publish times shouldn't be touched as they can be specified by a user.

I wouldn't necessarily call this a bug.
In the reported case I definitivly see not so.

What do we do:

1. We want to create a new article with content in it from an already existing article ... to work with it further on.
2. So we edit the source-article and use the "save2copy" function to create the new article.
3. The new article is created and the editor goes into it.
4. Now we can work further in the new article.

In 99% of all cases, the user forgets to set the creation-date/-time explizit.
So it is more useful to do this automatically.

The result must be the same, as when we do it in single steps like this.

1. Open source-article an put the content into scratch.
2. Close source-article
3. Create a new article by the joomla standard-process.
4. Paste in the content
5. Save the new article.

If you do it in single steps,
creation-date/-time is the actual date/time.
saving-date/-time is the saved date/time.

When doing it via "save2copy"
creation-date/-time is the source date/time. .... and that is wrong !!!!!!!!
saving-date/-time is the saved date/time.

You're proposing to alter a system wide behavior in this case. When an item is copied, the entire record is copied as is with the only modifications being to unpublish the item and change the title/alias to fit uniqueness rules if need be. As the current time is used only if a time is not specifically input into those fields, you're also suggesting that the copy process removes the created time, modified time, and published time. Making this change would not affect only articles; all extensions inheriting from the core MVC layer would be affected by this change. And I personally don't believe it is a change that should be made; it alters a core behavior and makes my data input questionable. If I open an article, change the title, remove the alias, and change the created time before clicking "Save as Copy", I expect my copied record to have those changes and the original record to be unchanged; with your suggestion my created time would be lost.

.... the create/publish times shouldn't be touched as they can be specified by a user

The create/publish times shouldn't be touched by a user. !
That are system-nearly times, so they should only be touchable by a admin.

I expect my copied record to have those changes and the original record to be unchanged; with your suggestion my created time would be lost.

I can't follow that in details and you may be right, but that is user-controlled and hand-made and therefore miles away from an automatized IT-process.

I'd say that's a totally separate issue then if you want to suggest that the created/publish times should be ACL limited. As is, anyone who has permissions to create/edit content on a site has the ability to specify these items.

There is no way to know if the time specified was system generated or user input. So the options are to either always reset the time or never reset it.

Hi,

sorry, but by closing the problem it is not resolved and it will continue to be wrong, because you get two different creation-dates, when creating an article about two different ways.

1. Create an article with the "new-button" and look to the creation date.
2. Do the same opening an existing article, make changes to the new content and press the save2copy-button. Then take a look to the creation-date.

In the first way, the creation-date is set to the date of the act. day in an automatic joomla-process..
In the second way the creation-date stays to that of the copied article. In that way the date isn't changed. It must be changed manually by the user. I guess, this will be forgotten in more than 90% of all cases.

One result therefore is, that the "newest article"-modul will not show the save2copy-created article without manually update the creation-date. That is "IT by hand" - far away from any automatic process which could be easily done be joomla itself.

Hi,
The saveascopy behaviour may be technically correct to copy accross the original created datestamp of the article, but from a practical stand point I agree with user hgh-esn, that it should create a new current datestamp.