See the whole site Free
Fix at the source, with site parts
Headers, footers, menus, synced patterns and widget areas are checked on their own, so a problem on every page is shown once and fixed once.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Lumtera checks the parts of a site that appear on many pages as objects of their own: template parts, synced patterns, navigation menus, classic menus and widget areas. They are checked when they are saved, when the theme changes, straight after Check all content, and from WP-CLI with wp lumtera scan --parts. Up to 200 parts are checked in one run, and the screen says if any were left out.
The Content report has a Site parts view next to By page and By issue. It lists each part by name and type, the theme it comes from, its issues by severity and a link to where it is edited, such as Open in Site Editor or Edit the menu. Check site parts now runs the check on request, and parts that could not be checked are listed with the reason. On pages, issues that come from a shared part say so, for example "Comes from Footer (template part) — fix it once there".
In the By issue view, when a group of findings comes from a template part, synced pattern, navigation menu or classic menu item, and the check has a fix, the group offers Fix at the source (clears N pages). The same review dialog shows the change, which says only that block or menu item changes and every page that shows it gets the change. After you apply it, Lumtera checks the pages that show the part again, in batches, and reports how many are clear.
Why does it matter?
An unlabeled link in the footer shows up on every page. A report that lists it 400 times makes a small job look huge, and fixing it post by post is pointless because it does not live in any post. It lives in a template part, a menu or a pattern that every page shares.
What do you get?
- Template parts, synced patterns, navigation menus, classic menus and widget areas are checked as parts of their own.
- They are checked when they are saved, when you switch themes, after Check all content, and with wp lumtera scan --parts.
- A Site parts view in the Content report lists each part with its issues and a link to where it is edited.
- Issues on a page say where they come from, such as "Comes from Footer (template part) — fix it once there".
- Fix at the source changes the part once, then checks every page that shows it again.
How does it work?
-
Open Site parts
Under Lumtera → Checks → Content, switch to Site parts to see each shared part and its issues, or choose Check site parts now.
-
Fix once
In the By issue view, a group that comes from a part Lumtera can change offers Fix at the source, with the number of pages it clears.
-
Watch the pages clear
After you apply the fix, Lumtera checks the pages that use the part again and shows how many still have the issue.
Who is it for?
-
A problem repeated on every page
An icon link without a name in the footer becomes one item to fix, not hundreds.
-
Writers and site builders
The My content view folds away issues from site parts, so writers see their own work. Site parts & code shows the parts to whoever looks after the theme.
-
After a theme switch
Every part is checked again in the background when you change themes, so new header and footer problems show up without a full scan.
Good to know
How it behaves, what it needs, and where its limits are.
- Theme template parts
- A part that still comes from the theme's files gets a customized copy, as the Site Editor would make. The dialog says that theme updates will not change it until you reset it. Undo deletes the copy, unless it was edited in the Site Editor since.
- Menus
- WordPress keeps no revisions of menu items, so Lumtera keeps the item's earlier text and settings with the change, for undo.
- Widgets and plugin parts
- Widgets are link-out only: fix them in Appearance → Widgets. Template parts that come from a plugin are fixed in the Site Editor.
- Permissions
- Template parts and menus need permission to edit the site's design (Appearance). A synced pattern needs permission to edit that pattern.
- Page-level checks
- Checks that look at the structure of a whole page, such as the heading outline, are not fixed at the source, because the right fix depends on each page.
Checks you will see here
-
WCAG 2.4.4 · AError
Link has no text
-
WCAG 2.4.4 · ANeeds review
Link text is vague
-
WCAG 1.1.1 · AError
Image has no alternative text
Questions
Something else on your mind? Contact support
What happens when I fix a theme's template part?
Lumtera saves a customized copy of the part, as the Site Editor does. The dialog explains the trade-off: theme updates will not change that part until you reset it in the Site Editor. Undo deletes the copy, so the theme's own part is used again.
Can it fix widgets?
No. Widgets are checked and listed, but Lumtera does not change them. It links you to Appearance → Widgets, where one change fixes every page with that widget area.
Does marking where content comes from change my pages?
No. Source markers are added only while a signed-in user who may use review mode is checking a page, and those responses are never cached. Visitors get the page as usual.
How many pages are checked again after a fix?
The pages that had the issue stored, up to 5,000. You can close the dialog while it runs; the rest continues in the background.
More in “See the whole site”
-
Free
Site-wide report and bulk checking
Check every post, page, product and site part, then see the score, errors, review coverage and the issues that repeat across the site. Export it as CSV.
-
Free
Honest coverage meter
Next to every automated score, a meter shows how many WCAG 2.2 A/AA criteria the checks cover, how many have evidence and how many need a person.
-
Free
CSV export of the content report
Download the Content report as a spreadsheet, one row per issue, with your filters applied. Free, and limited to what each person may see.
Start with the free plugin today
All 69 content checks and 33 whole-page checks, fixes you approve with undo, and the site report — free, with no account and no page limits.