Skip to main content
Jahia Store
EN

Site History

community
Download 0.3.0

Information

Module ID
site-history
Group ID
org.jahia.pm.modules
Status
community
Category
Content Features
Author
rgauthier@jahia.com
Developer website
http://www.jahia.com
Requires Jahia
8.2.2.0
Released
2026-10-26
Source
https://github.com/Jahia/site-history
Tags
  • history
  • audit trail

Site History lists the content history of a whole Jahia site in one table in jContent, so you see who changed which content, and when.

The History tab of jContent shows the history of one content item at a time. Site History reads the history that Jahia already records, and it lists every history entry of the site in one paginated table, newest entry first. The module stores no data of its own.

Features

  • The filter row selects the entries by date range, user, path and action. The User filter and the Path filter open the pickers of jContent.
  • A click on a column title sorts the table by date, user, property, action, path, UUID or message.
  • The column menu shows or hides each column: Date, User, Name, Content type, Property, Language, Action, Locate, Path, UUID and Message.
  • The Locate link of an entry opens jContent on its content item and selects it.
  • The GraphQL field siteHistory of the JCRNode type returns the same entries, with the same filters and the same sort.

Access

Site History opens from the Additional accordion of jContent. The module adds the permission viewSiteHistory, and the roles site-administrator and server-administrator hold this permission after the install. A user without viewSiteHistory does not see the page and gets no entry over GraphQL.

Requirements

  • Jahia 8.2.2.0 or later. Jahia ships the 3 modules that Site History needs: default, graphql-dxm-provider and jcontent.
  • Derby and MariaDB have first-class support. MySQL, PostgreSQL, Oracle and Microsoft SQL Server have best-effort support.

Limits

  • Jahia 8.2.4.0 deletes the history entries that are older than 13 months. On Jahia 8.2.3, a purge in December keeps 1 year of entries.
  • The module does not filter the entries by ACL. A user with viewSiteHistory sees every entry of the site, including the entries of content that this user cannot read.
  • A moved content item keeps its old path on its old entries.
  • Jahia records the default workspace only, and Jahia does not record the actions of the user system.
  • With 2,000,000 entries on MariaDB and Jahia 8.2.4, a GraphQL request for 20 entries took up to 5.4 seconds with no filter. The same request took 0.12 seconds with a date filter of 24 hours.

The README of the module lists every limit: github.com/Jahia/site-history#limits

Screenshots

Dependencies

Depended on by

Nothing depends on this module.

Versions

Requires Jahia 8.2.2.0Released 2026-10-26