WordPress 7.1 updates jQuery UI to 1.14.2. Plugins with datepicker, dialog, autocomplete, sortable, draggable, tabs, custom themes, or private jQuery UI assumptions may show layout, focus, event, localization, or saved-value regressions even when the admin screen initially loads.
Use this for plugin admin screens, booking calendars, reporting filters, event dates, modal settings, sortable builders, and custom jQuery UI themes.
Quick answer
Inventory each component and the script or theme that owns it. Test pointer and keyboard open, select, escape, tab order, focus return, localization, time zone, min and max date, mobile viewport, sorting, modal stacking, save, reload, and another admin page. Record console errors, DOM ownership, loaded versions, visual result, accessibility result, saved value, and rollback path.
What to check first
- List every plugin admin route that enqueues jQuery UI components, themes, translations, extensions, or private patches.
- Record WordPress, plugin, browser, locale, time zone, component, script handles, CSS handles, and loaded jQuery UI versions.
- Test mouse, touch, keyboard, escape, tab order, focus return, localization, date boundaries, sorting, drag cancellation, and modal stacking.
- Save and reload each value, then visit another admin screen to detect leaked styles, duplicate bindings, and global event changes.
- Compare WordPress 7.0 and 7.1 evidence, isolate the owning plugin, and test the smallest supported fix.
Diagnostic table
Use this table to connect the observed behavior to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Identify the plugin and handle that owns the failing component. | List every plugin admin route that enqueues jQuery UI components, themes, translations, extensions, or private patches. | Datepicker values respect locale, time zone, boundaries, save, and reload. |
| Remove duplicate initialization and update unsupported markup assumptions. | Record WordPress, plugin, browser, locale, time zone, component, script handles, CSS handles, and loaded jQuery UI versions. | Dialogs trap and return focus and close by the supported controls. |
| Scope custom jQuery UI CSS to the plugin admin route. | Test mouse, touch, keyboard, escape, tab order, focus return, localization, date boundaries, sorting, drag cancellation, and modal stacking. | Sortable and draggable actions persist once with no duplicate event. |
| Restore keyboard focus, localization, and saved-value behavior. | Save and reload each value, then visit another admin screen to detect leaked styles, duplicate bindings, and global event changes. | Custom themes stay scoped and unrelated admin screens remain unchanged. |
Why this usually happens
- Plugins can depend on undocumented markup or class names.
- A bundled custom theme may override updated core styles globally.
- Duplicate component initialization can attach events twice.
- Visual success does not prove keyboard focus or saved-value correctness.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
route,component,action,console,focus,visual,saved,result
booking,datepicker,keyboard,none,return,pass,2026-09-01,pass
reports,dialog,escape,none,lost,pass,n/a,fail
builder,sortable,drag,double-bind,ok,duplicate,2-1-3,fail
settings,tabs,rtl,none,ok,pass,current,pass
Test scenarios to run
Run the same controlled fixture across these branches. Write down the expected result before testing so a surprising response is easy to identify.
| Scenario | Fixture | Expected result |
|---|
| Datepicker | Keyboard and localized date | Selects, saves, reloads |
| Dialog | Open, tab, escape, close | Focus stays trapped and returns |
| Sortable | Drag, keyboard alternative, cancel | Order persists once |
| Custom theme | Plugin CSS plus core 1.14.2 | No clipping or global leak |
Safe fix order
Use a sequence that makes each result easy to prove. Stop when new evidence changes the scope or owner of the problem.
- Identify the plugin and handle that owns the failing component.
- Remove duplicate initialization and update unsupported markup assumptions.
- Scope custom jQuery UI CSS to the plugin admin route.
- Restore keyboard focus, localization, and saved-value behavior.
- Retest the component matrix on WordPress 7.1 before promotion.
Decision rule
Approve the plugin when each component works by pointer and keyboard, saves the expected value once, returns focus correctly, and does not leak scripts or styles into unrelated admin screens.
Production verification checklist
- Datepicker values respect locale, time zone, boundaries, save, and reload.
- Dialogs trap and return focus and close by the supported controls.
- Sortable and draggable actions persist once with no duplicate event.
- Custom themes stay scoped and unrelated admin screens remain unchanged.
Field notes
- Test one non-English locale and one right-to-left layout when supported.
- Capture computed style ownership for clipped controls.
- Do not replace core jQuery UI globally as a quick fix.
Questions teams ask during testing
Can this be tested on production?
Use production for read-only confirmation and one narrow synthetic fixture that cannot charge a card, email a real customer, expose personal data, or change inventory. Perform destructive repairs, upgrades, cache changes, and schema work on staging first.
What evidence should the report keep?
Keep exact versions, UTC timestamps, stable synthetic IDs, expected and actual results, the decision owner, rollback point, and final verification. Redact customer data, credentials, tokens, addresses, and private infrastructure details.
When is the task complete?
Complete the task when the primary user path passes, downstream records reconcile, failure branches are understood, monitoring is active, and an established owner page links to the new guide in context.
Mistakes to avoid
- Changing production before recording exact versions, UTC timestamps, stable fixture IDs, current settings, and a reproducible baseline.
- Treating one successful screen as proof that background jobs, APIs, caches, roles, reports, and downstream records agree.
- Deleting logs or identifiers before the failure boundary, business impact, rollback point, and accountable owner are known.
- Testing only an administrator session instead of the devices, roles, networks, data states, and failure paths real users have.
What to tell the client or owner
Give the site owner the affected versions, exact synthetic fixture, UTC timeline, before and after evidence, current cause class, decision, rollback point, unresolved risks, and next review date. State which measurements prove success and which observation window remains open.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, security, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, fix a WordPress plugin compatibility issue.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references