WordPress audit log for one site

A WordPress audit trail is a time-ordered record of actions on a site: what changed, who did it and when. It helps explain an incident, prove maintenance work and spot unexpected changes. In CMDPress, each connected site has its own activity view, so you can read one site’s actions in order without the rest of the workspace mixed in.

Open the site’s activity log and read the entries around the time of the change. In CMDPress, the site activity view lists actions for that one site with timestamps and the user behind each one. If the answer is not there, the site’s logs and the wider workspace history are one step away.

Start at the moment the problem began and read backwards. CMDPress shows one site’s actions in order, so you can see what changed just before an incident or during a maintenance window. Then open the site’s logs, such as debug.log, to match errors to the same timestamps before you decide on a fix.

Site activity covers one connected site, while workspace history is the wider record across the sites in your CMDPress workspace. Use the site view when you need a precise timeline for one client. Switch to workspace history when the cause may sit wider, such as a change made across several sites at once.