Legacy Knowledge Base
Published Jun. 30, 2025

When moving a web content to another folder, the modification date of the web content is updated

Written By

Rafael Regner

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

  • When moving a web content from a folder to another, the modification date of all versions of the web content are updated.
  • Is this an expected behavior?

Environment

  • Liferay DXP 7.2
  • Liferay DXP 7.3

Resolution

  • When moving a web content to another folder, it is expected that the modification date of all versions will be updated.
  • As you can see in the code, when moving an article, all versions of this article are recovered and later, both their new folderId and their new treePath are updated:
    List<JournalArticle> articles = journalArticlePersistence.findByG_A(
    groupId, articleId);

    String treePath = null;

    for (JournalArticle article : articles) {
    article.setFolderId(newFolderId);

    if (treePath == null) {
    treePath = article.buildTreePath();
    }

    article.setTreePath(treePath);

    journalArticlePersistence.update(article);
    }
  • This route update is what causes the modification date update for all versions.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base