Dango System Utilities

2.6.0

• New: Background Jobs, on the Tools tab and summarised on the Overview. Every scheduled job is listed with what it did last time, when it runs next, and a “Run now” button — so nothing has to wait for WP-Cron, and it is clear whether a job actually ran. A long job runs in short passes with a progress bar instead of hitting PHP’s time limit.
• Fixed: help bubbles were drawn underneath the admin menu. The “?” sits beside the sidebar, the bubble was centred on it, and a duplicate style rule stacked it below the menu. Bubbles are now positioned against the screen, kept clear of the menu and admin bar, flip below the “?” when there is no room above, and open with a tap on touch screens.
• Search Analytics: a “What is counted here” panel on the report. Searches made while logged in as an administrator are deliberately not counted — including the report’s own Test buttons — which is the usual reason a count seems not to move. The panel says so, along with the bot, term-length and page-cache rules.
• Search Analytics: “Check again now” runs every term under Unsuccessful Searches against your site as a logged-out visitor would, and marks the ones that return results today. The recorded history is left untouched. The Results column is now labelled “Results (last search)”, which is what it always showed.
• Search Analytics: weekly maintenance compared search dates against UTC rather than the site’s own date, so on sites far from UTC the retention window ran a day early or late.
• New: remove jQuery Migrate on the front end. Admin screens keep it.
• New: stop loading the Dashicons font for logged-out visitors. Stylesheets that declare it as a dependency still get it.
• New: disable application passwords — long-lived API credentials that are checked without the login form, so CAPTCHA, lockouts and two-factor never see them.
• The Add-ons tab now totals what this plugin includes and what the add-on adds, with counts per group.
• The remaining confirmation prompts in the Cron Manager and data purging tools no longer use inline onclick handlers; they go through the plugin’s enqueued admin script like every other prompt.

2.5.8

• Settings screens are grouped and boxed. Every module, including the ones the paid add-on contributes, now sits in its own card under a section heading, instead of running together as one unbroken column of fields — the Security tab in particular was a wall of inputs with nothing marking where one feature ended and the next began.
• Every setting has help. The “?” bubble now covers all of them, not just some, and each says what the option does, what WordPress does by default, what we recommend, and what you give up by turning it on.
• Options with a real consequence say so where you set them, in a coloured note: an SVG upload can carry script, a 2FA role list can lock out anyone whose email is broken, a maintenance page hides the site from search engines, a published WhatsApp number is public and messaging customers first is regulated, a Cloudflare token should be scoped rather than global.
• Modules worth switching on for most sites carry a “Recommended” tag.
• New on the Overview tab: a recommended-settings checklist that says which of them are not in place, what each one is for, and applies them in one click. Nothing is changed until the button is pressed, and every change is named first.
• Roles and post types are chosen from a list of what the site actually has, rather than typed as comma-separated slugs. Getting a role name wrong is how people locked themselves out of 2FA.
• Two-factor authentication is configured in one place. It appeared under both Security and Privacy & Users, the same field rendered twice, with nothing to say which was real.
• Settings for a module you do not have installed are no longer rendered. On the Integrations and Privacy tabs, the section headings were conditional but the fields underneath them were not, so one installed integration displayed the settings for all ten.
• Quick search now matches module names as well as field names, hides a section heading whose sections have all been filtered out, and says when nothing matched instead of showing a blank page.
• The save button follows you down long tabs, and leaving a tab with unsaved edits now asks first.
• New: disable pingbacks and trackbacks. Ends pingback spam and self-pings, and stops the site making an outbound HTTP request to every URL you link to — the behaviour that lets a WordPress site be used to attack someone else.
• Channel Performance now separates paid advertising from free traffic out of the same place. An Instagram ad and a link in an Instagram bio were one row; they are now “Instagram Ads” and “Instagram”, counted separately, so ad spend is never reported as organic reach. Read from the campaign medium WooCommerce already stores (cpc, paid_social and the like) — a row is only called “Ads” when the data says so, and an ad whose link was never tagged with a medium is still counted as an ordinary tagged link rather than guessed at. The medium is printed under every name, and included in the add-on’s CSV export.
• Channel Performance: a source reached two different ways no longer appears twice under one identical name. Instagram from a link and Instagram from a tagged campaign link are still counted separately, because merging free traffic into paid would misreport what advertising is doing, but the name now says which is which. Names that do not collide are untouched.
• Search Analytics: “Last 7 days” and “Last 30 days” covered 8 and 31 days. Both the on-screen reports and the CSV exports had their own copy of the same off-by-one; they now share one definition and cover exactly the days they name.
• Search Analytics: “Avg results / search” averaged one value per keyword per day, so a term searched five hundred times counted the same as one searched once. It is now weighted by how often each term was actually searched.
• Search Analytics: the zero-result rate and the unsuccessful-searches table disagreed — a keyword that returned nothing last week but works today was counted as a failure by the rate and left out of the list of failures. Both now use the same definition.
• Search Analytics: the recorded result count could only ever go up, and any secondary search on the page — a sidebar widget, a “related searches” block — was allowed to raise it. A page listing three results could end up recorded as forty. The count now comes only from the query whose results the visitor was looking at.

2.5.7

• Traffic sources in Channel Performance are now named the way a person would say them. WooCommerce records whatever the browser reported, so the report used to read “Referral: Com.google.android.googlequicksearchbox” and “Organic: Google”; it now reads “Google App & Discover (Android)” and “Google Search”, covering search engines, social networks and their apps, messengers, AI assistants, email tools, marketplaces and payment-page returns.
• The value WooCommerce actually recorded is printed under each name, along with how the visitor arrived, so every row can still be matched against WooCommerce’s own Origin column and nothing is hidden behind the friendlier wording.
• Different spellings of one source — facebook.com, m.facebook.com and the Facebook Android app, for example — now count as a single row. Organic search is never merged with a campaign tag of the same name, so free traffic is never counted as paid.
• Android apps are covered too — the Gmail, YouTube, Instagram, Facebook, Messenger, WhatsApp, Telegram, TikTok, X, Pinterest, Reddit, LinkedIn and Snapchat apps, the mobile browsers that report themselves as the referrer, and the link shims social platforms redirect through.
• A source with no entry in the list is still shown, tidied but never dropped, so nothing goes missing from the report.
• Naming is done while the report is drawn, from data already fetched: no extra queries, no lookups, nothing scheduled, nothing stored.
• The add-on gains Channel by Device: the same orders split across phones, tablets and computers, so a source that completes on a computer but fails on a phone — usually a checkout problem rather than a traffic problem — is visible. Its CSV export covers it too.

2.5.6

• City Performance now supersedes the weaker city table the paid add-on used to draw. That one read the billing address rather than the shipping one on a delivery report, silently dropped every order with no city set, listed “lahore” and “Lahore” as two places, and measured its lost rate against orders that had not settled yet. It has been removed rather than kept alongside.
• The add-on now cross-references the two instead: which traffic sources actually convert in which cities, so a channel that looks healthy overall but fails in one city is visible. Pairings too small to read anything into are hidden.
• The add-on’s CSV export now covers channel performance, city performance and the channel-by-city crossing.

2.5.5

• Fixed Channel Performance reporting every order as “Unknown”. WooCommerce does not store the Origin string shown in the orders list — it composes it at display time from two separate meta values — so grouping on an origin key matched nothing. Channels are now grouped on the real attribution data and labelled the same way WooCommerce labels them. The Pro dashboard’s orders-origin widget had the identical bug and is fixed too.
• Sources that differ only by capitalisation are now merged into one row instead of appearing as separate channels.
• New: City Performance, alongside Channel Performance — orders received versus delivered per destination city, using the shipping city and falling back to billing. City spellings differing only by case or spacing are merged.
• Search dates are now bucketed in your site’s timezone instead of UTC. “Today” previously began at UTC midnight, so on a UTC+5 store everything searched before 5am local was filed under the previous day.
• The Search Report now shows “Searches Today” and “Searches Yesterday” as term lists with a count each, replacing the raw timestamped log. The full log remains available as a CSV export.

2.5.4

• Fixed inflated search counts. A search was recorded for any search query running during an AJAX request, so a theme with live search suggestions logged one search per keystroke — typing a seven-letter word recorded seven searches. Only a real front-end search page view is counted now; REST, XML-RPC, cron, feed and robots requests are excluded too, and a secondary query can still correct a result count but can never create a search. Existing recorded data is unchanged.
• Added a minimum search term length (default 2 characters) so one-letter fragments from type-ahead boxes are not recorded as searches.
• Widened crawler detection to cover more SEO, AI and uptime-monitoring agents.
• New: Channel Performance in Order Analytics — orders received versus actually delivered for each traffic source, with completion rate, lost and refunded counts, realized revenue and average order value. Reads WooCommerce’s own Order Attribution data; this plugin sets no cookie and stores no visitor data of its own for it. Completion rate is measured against settled orders, so recent timeframes are not penalised for orders still in progress.
• The purge and cache tools now report what they removed instead of returning silently.
• “Clear Cache” now removes every cache the plugin owns, including the hash-keyed order analytics caches that previously lingered until they expired on their own.
• Uninstall now sweeps the plugin’s remaining transients, including orphaned timeout rows.