Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Modified date not match the author of a web content, document or any other asset.

Written By

Daniel Carrillo Broeder

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The author displayed for content/documents is inconsistent when modifications are made by users other than the original author.
    • When a user edits and publishes the content, the displayed author is correctly updated to the user who published the latest version.
    • However, if the action is only "Save" (e.g., modifying permissions), themodified date is updated but the displayed author remains the original creator of the content, even if a different user made the modification:

Environment

  • Liferay DXP 7.0, 7.1, 7.2, 7.3, 7.4
  • Quarterly Releases

Resolution

  • This behavior is expected:
    • The displayed author is updated only when a new version of the content is published.
    • Some actions like modifying permissions do not trigger the creation of a new content version, hence the author remains unchanged but the modified date is updated to be considered in  partial exporting/import processes like Staging or Publications.
  • A Feature Request has been submitted to address this behavior and provide more clarity to users  in future versions.

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?