← Back to modules

nexya activities WordPress activity log, field by field

Who changed what on the WordPress site, and when. Down to the ACF fields, with the before and after values — and, with Pro, the rollback button

  • It goes down into the ACF fields Not just “the Contact page was modified”, but which field, in which row of which repeater, with the old value and the new one facing it. That is what other journals do not show
  • Undo in one click With Pro, a reverted content change goes back to what it was — title, text, status, taxonomies, ACF fields — and can be replayed
  • It ignores its own plumbing The suite’s internal handling does not clutter the journal. You read what people did to the site, not what the plugin did to itself
  • Menus and plugins too Menus created, renamed, or deleted, plugins activated, core updates. These are the changes you look for when a site starts behaving differently
nexya activities on video: WordPress activity log, field by field 0:25

What it can do

A WordPress activity log that shows what changed, field by field

Who changed what, and when, right down to ACF fields, with the value before and after. And with Pro, the button to go back.

The log

What people did to the site, in order

Content published, edited or deleted, menus renamed, plugins activated, updates, accounts created or given a new role: each row says who, what and when. The plugin’s own internal operations do not clutter the list.

  • Filtered by person, type and date
  • Thirty days kept, up to a year or more with Pro
  • Log export for a client or an audit
The log nexya activities
  • Marie Dupont edited 2026 pricing Content Page 27.08.2026 14:32
    Title Our pricing 2026 pricing
    Status Draft Published
  • Marie Dupont created Our offices Content Page 27.08.2026 09:41
  • Johan updated Advanced Custom Fields PRO Plugin 26.08.2026 22:14
  • System updated WordPress WordPress 26.08.2026 04:02
  • Johan tested the account claire.m Account Account test 25.08.2026 16:05

The journal keeps thirty days. It ignores its own plumbing: what you read there is what people did to the site.

The detail

The old value and the new one, side by side

Not just “the Contact page was edited”: which field, in which row of which repeater, with what it held before. With Pro, a change is undone in one click — title, text, status, taxonomies, ACF fields — and can be replayed.

  • ACF and nexya custom fields included
  • With Pro, undo then replay
  • Reordered pages logged too
The detail of one change nexya activities
Marie Dupont edited 2026 pricing Content Page 27.08.2026 14:32
Section heading Contact us Drop us a line
Plans 3 item 4 item

Row 2 changed

Price 890.— 790.—
Highlighted No Yes

Row 4 added

Label Bespoke
Price 1 490.—
Pro

Go back to the previous state, or do it again. The journal keeps both states, it guesses neither.

Undo this change Replay

Undo

A mistake is undone in one click, without restoring a backup

With Pro, each content change in the log has an Undo button. The title, text, status, taxonomies or an ACF field go back to their previous value, without touching the rest of the site, and the undo can itself be replayed.

  • Only the targeted change is reverted
  • Retention up to a year or unlimited
  • The undo is logged too
Going back nexya activities
Change Action
Contact · Title 2 hours ago Undo
Home · Figures, row 3 yesterday Undo
Pricing · Status Monday Replay

With Pro: title, text, status, taxonomies and ACF fields come back in one click, and an undo can be replayed.

And everything else, already included

  • Menus Created, renamed or deleted, with their author.
  • Plugins and themes Activations, deactivations and updates logged.
  • Accounts Created, deleted or given a new role, with who did it.
  • Account tests When an admin takes over an account with nexya roles, it is logged.

Why ACF details matter

On a site built with ACF, most of the content doesn’t live in the editor but in fields — often nested in repeaters or flexible content. A log that just says “the page was modified” is useless: the question is always “modified where?”. The module compares field by field and displays the path, making it possible to see that a schedule changed in the second row of a table, and nowhere else.

What it records

Content created, modified, and deleted, across all types. Menus created, renamed, or deleted. Plugins activated, deactivated, updated. Core updates. High-privilege accounts created, deleted, or changed in role. Each entry carries the account author and the exact time.

What it intentionally does not record

Neither the plugin’s internal operations, nor role permission settings, nor technical details that no one can interpret. A log read by a client must contain what they can understand and act upon. The rest is noise, and noise makes people close the page.

Free

Filterable journal for thirty days, ACF detail, export

Pro

Undo and replay, retention up to a year or unlimited

On the blog

Our guides: WordPress activity log

Guides · 5 min read

Hacked WordPress site: steps to clean it and prevent reinfection

Your WordPress site has been hacked: this guide gives you the order of operations to clean it up without leaving a backdoor, and then to prevent it from being reinfected. It also details what nexya does to secure the site afterward, and what it does not do, since it does not clean up malware.

  • nexya does not clean up malware: cleanup is done manually, with your host, a specialized tool, or a professional.
  • Close the site and export the database before touching the files; the Maintenance module does both.
  • Replace the core, plugins, and themes with official copies rather than searching for infected files one by one.

Read the post

Guides · 5 min read

WordPress plugin flagged as vulnerable even though it is up to date: how to decide

A WordPress plugin reported as vulnerable while it is up to date is not necessarily a false positive, nor necessarily a real vulnerability. This guide shows how to decide in a few minutes, then what to do in each case with the nexya Security module.

  • A vulnerability check compares the name and installed version against a list of known vulnerabilities; an error in the list is enough to produce a false positive.
  • An up-to-date version can also be genuinely vulnerable when no patch exists yet.
  • The vulnerability report decides: affected versions, patched version, publication date.

Read the post

Guides · 4 min read

Updating WordPress plugins: fewer extensions, fewer risks

Updating WordPress plugins takes time because each extension has its own author, its own pace, and its own risks. This article shows how to reduce the number of plugins to track, and then how to prepare, check, and monitor each update with nexya.

  • The cost of a plugin is paid with every update: versions to track, potential conflicts, vulnerabilities.
  • nexya groups common tasks into a single plugin, and a disabled module executes no hooks.
  • Before an update: clean the database, export it, display the maintenance page.

Read the post

Get started

nexya activities in three steps

  1. Switch on nexya activities In the nexya hub: the log starts recording at once.
  2. Let the site live Content, custom fields, menus, plugins, updates: each change is recorded with its author.
  3. Find what changed Filter by person, date or content, and compare the before and the after.

nexya activities is in the free extension, on as many sites as you want.

Get the free version View pricing

FAQ

Everything about nexya activities

The nexya activities log records every change with its author, the date and the detail: which field, the old value and the new one.

Yes, even inside repeaters: which field, in which row, with the before and after values.

With Pro, yes: one click puts the content back as it was, text included, and the change can be replayed afterwards.

The same idea, with the detail of custom fields and, in Pro, one-click rollback. The log also ignores the suite’s internal work, keeping only what people did.

Thirty days in the free version, longer with Pro. The log can be exported at any time.

Yes: by account, by type of action, by period and by keyword. The log can then be exported for a client or an audit.

Yes, along with activations, deactivations and core and theme updates. It is often the first lead when a site starts behaving differently.

No. It only writes when something changes in the admin, never during a reader’s visit, and old entries are removed on their own.

The suite

Other modules

nexya Checkout

Pro

A step-by-step WooCommerce order, on a page of its own, with the cart on the side and suggestions at the right moment.

nexya Invoice

Pro

WooCommerce PDF invoices in your colours, attached to the e-mails, with the Swiss QR-bill at the bottom of the page.

nexya forms

Pro

Forms built field by field, with conditions and in multiple steps — paid online if needed, and every response saved on the site.

nexya translate

The site in several languages, WooCommerce shop included: every content with its versions, one address per language, and the site’s texts translated in one place.

nexya popup

Popups built section by section, opening at the right time — and which, with Pro, can close the shop and forms while they are active.

nexya custom fields

Fields that belong to you, stored in their own tables — and read in a single query per page.

nexya aris

Audience figures measured by the site itself — without Google, without Matomo, without any stored IP address.

nexya mailya

Pro

Newsletters written on the WordPress site, with your articles inside — sent in the background, at the pace your server can handle.

nexya media

Background thumbnail regeneration, in batches, that continues even when you close the tab — and notifies you when it's finished. With Pro, folders to organize your media library.

nexya hub

The dashboard that brings together all nexya extensions. One module you turn on, one module you turn off — and nothing runs on the WordPress site while it's off

nexya dashboard

The WordPress administration as the client sees it: menus reduced to the essentials, the admin bar tidied up — and, with Pro, dashboard colors all the way to the login page

nexya shortcuts

Duplicate, reorder, add — three actions performed on WordPress content lists so you never have to do them by hand again

nexya roles

WordPress rights organized under the content type they belong to, finally readable. And the menu reduced to what the person in front of it actually needs to do there.

nexya cookie

Cookie consent, and the blocking that goes with it. Nothing runs before the visitor agrees — no scripts, no embedded videos, no remote fonts

nexya seo

What the WordPress site tells search engines about itself — and what it displays when you paste its address somewhere. Written once, applied everywhere, verifiable before publishing

nexya mail

WordPress site emails actually get sent — and we know which ones didn't, with the exact reason provided by the SMTP server

nexya redirects

404 errors identified during visits, along with the number of hits to know which ones matter, and the 301 redirection that fixes them. With Pro, the target is suggested before you even look for it.

nexya security

Setting up HTTP security headers without breaking the site, monitoring vulnerabilities in active WordPress extensions, and tracking file changes

nexya maintenance

Operations performed on the WordPress site, but not within it: closing it during maintenance, streamlining its database, making a backup

nexya performance

What each page costs the site, and the settings that lighten it: a query monitor on every page, options loaded on each visit, the Heartbeat, revisions

nexya cache

Pro

Every page kept as a file and served to the next visitor before WordPress loads — then discarded as soon as something changes it.