-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, 7.0.0 M5
-
Fix Version/s: 7.0.0 M6
-
Component/s: Core Infrastructure
-
Labels:None
-
Story Points:6
-
Fix Priority:3
-
Git Pull Request:
Audited and Staged Models create and modified dates are not always update correctly.
Steps (for User)
- Create a new user "test2".
- Check the modifiedDate column in the DB for that user.
select emailaddress, status, createDate, modifiedDate from User_;
- Update the first name of that user, modifiedDate column gets updated with current timestamp.
- Deactivate the user, modifiedDate column does not get updated with current timestamp.
Expected
After the user's status is changed (deactivated/activated), the user's modifiedDate column is updated with the current time.
Actual
After the user's status is changed (deactivated/activated), the user's modifiedDate column is not updated with the current time.
- causes
-
LPS-57317 Page Comments - "Edited" appears on every post
- Closed
-
LPS-55758 Cannot publish DLFileEntry because createDate is null
- Closed
-
LPS-56005 After activating staging, any existing webcontent cannot be edited
- Closed
-
LPS-56124 Default createDate and modifiedDate cannot be overridden in new entities using serviceContext
- Closed
-
LPS-56991 Blogs attachments modified date changes when we view the entry
- Closed
-
LPS-65497 UserLocalServiceImpl.updateModifiedDate doesn't set modifiedDate
- Closed
-
LPS-65531 User's modifiedDate is not set correctly during LDAP import
- Closed
- fixes
-
LPS-61428 Password export to LDAP doesn't work
- Closed
- relates
-
LPS-62788 Service builder throws error when plugin model implements hasSetModifiedDate
- Closed