Staging History deleted after a few days
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- After a few days, past Staging publication records disappear from the history list located in Site Administration > Publishing > Staging
Environment
- DXP 7.2, DXP 7.1, DXP 7.0
Resolution
- By default, Liferay is configured to keep the latest 50 staging records, including processes that are not completed within the Publishing > Staging page (i.e. navigating to Site Administration > Content & Data > Web Content > Staging and publishing changes)
- To override this setting, place a portlet-ext.properties file in [Liferay_Home]/tomcat-9.0.17/webapps/ROOT/WEB-INF/classes and set the following properties:
include-and-override=portlet-ext.properties
#
# Set the interval of the clean up process which will delete the draft export
# import configurations. Interval is specified in hours.
#
draft.export.import.configuration.check.interval=36
#
# Sets the number of draft export import configurations to keep by the clean up
# process. By default, it will keep the latest 50 draft export import
# configurations. Set this property to -1 to keep everything. Set this property
# to 0 to delete everything.
#
draft.export.import.configuration.clean.up.count=50
Did this article resolve your issue ?
