Try our conversational search powered by Generative AI!

StatusChangedBy on Version does not match SavedBy when Content is saved by system

Fixed in

EPiServer.CMS.Core 9.4.0

(Or a related package)

Created

Nov 10, 2015

Updated

Dec 04, 2015

Area

CMS Core

State

Closed, Fixed and tested


Description

In case a Content item is saved by the system, that is without a current user, the SavedBy field on the version is set from the ChangedBy property on the content item. This is not the case for the StatusChangedBy property.

If the item is saved by an active user, both these properties will have the same value.

Reproduction step:

  • Create a new page save and publish
  • Check the StatusChangedBy property on the saved version through the ContentVersionRepository, or check the value of the column 'NewStatusByName' of the just saved version in the tblWorkContent in the database. It should have your username as it's value, the same as the 'ChangedByName' column.
  • Create a scheduled job that updates the same page
  • Let the scheduled job run by itself
  • Check the StatusChangedBy property on the saved version through the ContentVersionRepository, or check the value of the column 'NewStatusByName' of the just saved version in the tblWorkContent in the database. It will be empty, unlike the ChangeByName column.