Query Wrangler 1.5.58 is a security release. Site owners using this plugin should update promptly, then review the new callback approval setting and test the custom views that matter to their visitors.
The plugin’s release notes describe stronger access controls and a safer approval model for callbacks used by custom queries. The update is especially important for sites where more than one person can sign in to WordPress or manage content.
What to do first
- Confirm that the affected site uses Query Wrangler.
- Use your normal maintenance window and recovery controls, then update the plugin to version 1.5.58 from the WordPress dashboard.
- Keep trusted administrators available while you complete the post-update checks below.
For a steady, site-owner friendly update process, follow our WordPress update guide. Do not make unrelated theme, server, or account-permission changes during this focused update.
Review the new callback approval setting
Version 1.5.58 introduces an Allowed Callbacks setting. Existing callbacks saved in your queries are retained for continuity, while callbacks added after the update must be approved by an administrator. Review this setting carefully:
- Keep only callbacks your site needs for its published views.
- Remove entries you cannot identify or no longer use.
- Limit administrator access and check that lower-privilege accounts have only the access they need.
If your site uses a developer-maintained callback, coordinate with that developer before removing it. The aim is to preserve the expected public view while keeping the approval list intentional.
Verify the site after updating
- Open representative pages that display Query Wrangler views, including any search, archive, or filtered content pages.
- Confirm that the expected items, paging, and public layout still work.
- Have an administrator check the plugin settings and any custom view previews.
- Review WordPress administrator accounts and remove access that is no longer required.
Document the update version, the checks you completed, and any approved callbacks. That small record makes later troubleshooting much easier without collecting a full-account archive for a routine plugin update.
When to get help
Ask for help if a key view stops rendering, a callback is unfamiliar, or the site has custom code that depends on Query Wrangler. Our WordPress support team can help scope the update, verify the public result, and keep the change focused.
Official release information
Review the Query Wrangler listing and changelog on WordPress.org for the vendor’s current release notes. This guide is defensive maintenance guidance; it intentionally omits operational details that could be misused.
