Antrun Inquiry Report

Changelog

2.3.0

• Added a one-click “Reconnect” flow: disconnecting now remembers the site’s email locally, and the
  settings page offers a dedicated Reconnect button instead of sending the site back through the
  trial/paid signup forms as if it were a brand-new customer. Restores the existing plan exactly as
  it was — nothing is lost.
• The account’s identity is now the site itself rather than its email address, so a site can change
  its contact email at any time without it affecting its plan. (Email still controls where reports
  are delivered by default.)
• The connected-account view now shows the site URL alongside the account email, and the Disconnect
  confirmation names the specific site being disconnected.
• The trial/paid signup email fields no longer default to the site’s WordPress admin email — they’re
  blank with a “you@example.com” placeholder instead, so the field always reflects what the customer
  actually typed.
• The “Go Straight to Inquiry Report Standard” button now matches the primary blue styling of the
  free-trial button.

2.2.10

• Added a nonce check to the Stripe checkout-success handler (handle_stripe_success), per wordpress.org
  review feedback. The one-time token in that URL proves a checkout was paid for, but not that this
  site’s admin is the one who paid — a CSRF using a token from any completed checkout (including an
  attacker’s own) could otherwise get an admin to attach their site to the wrong Stripe-backed account.
  The plugin now mints a nonce when checkout is initiated, the backend echoes it back in success_url,
  and this handler verifies it before doing anything with the token.

2.2.9

• Scoped every admin notice this plugin prints to its own admin pages only. The “requires Contact
  Form 7” warning previously had no scope check at all and would show on every wp-admin screen
  (dashboard, post editor, everywhere) for as long as Contact Form 7 was inactive; the
  connect/save/disconnect confirmation notice was similarly missing an explicit check, relying only
  on its own short transient lifetime and on every redirect already pointing back at this plugin’s
  pages. Neither showed up outside this plugin’s own pages in practice, but wordpress.org’s
  guideline against plugins that “hijack the admin dashboard” (Guideline 11) requires an explicit
  scope check regardless, so all three of this plugin’s notices now check the current screen.

2.2.8

• Added an Author URI (https://antrun.com) to the plugin header, ahead of wordpress.org’s
  trademark/ownership check on the “Antrun” name — one supporting signal that the wordpress.org
  account, the plugin, and the antrun.com site are all controlled by the same party. Doesn’t itself
  resolve that check — that requires a direct reply confirming ownership.

2.2.7

• Narrowed the internal prefix from “ANTRUN” to “ANTRUN_IR” (classes, functions, constants,
  options, table, hooks, menu slugs, etc.) so future Antrun-built plugins on the same site can’t
  collide with this one’s identifiers. Also fixed a bug from 2.2.6 where several admin-post action
  hooks were missed by that rename (their names were embedded inside a longer string and slipped
  past the search-and-replace), which would have made every account/settings form on this plugin
  silently fail; the backend’s Stripe checkout URLs were updated to match.
• Sites already running 2.2.6 need to reconnect again on the Settings page after this update, for
  the same reason as 2.2.6 (the stored option name changed again).

2.2.6

• Renamed every internal PHP class/function/constant, option, database table, cron hook, admin-post
  action, and admin menu slug from the “DIR”/”dir” prefix to “ANTRUN”/”antrun” — wordpress.org
  flagged the 3-letter prefix as too short and too common a word to reliably avoid collisions with
  other plugins/themes. No user-facing behavior change, but sites upgrading from an earlier version
  will need to reconnect on the Settings page, since the stored account data lived under the old
  option name.

2.2.5

• Renamed the plugin to “Antrun Inquiry Report” (slug antrun-inquiry-report) — wordpress.org flagged
  “Inquiry Report” as too generic/not distinctive for the directory.

2.2.4

• Ran the official Plugin Check (PCP) tool ahead of wordpress.org submission and fixed what it found:
  updated “Tested up to” (was blocking the plugin from appearing in search) and corrected a
  phpcs:ignore comment that was silencing the wrong sniff code, leaving a warning unsuppressed.

2.2.3

• Added an “External services” disclosure section and a data-use note in the description, ahead
  of a WordPress.org submission.
• Added a Screenshots section.

2.2.2

• Reports now show “Antrun Automation” as the provider instead of the underlying AI vendor
  (OpenAI/Anthropic), and no longer show the raw model name — which AI generates your report is
  an Antrun-managed implementation detail.

2.2.1

• The free trial is now limited to one per email address, on the backend — prevents repeated trial
  signups for the same customer.
• Site URL and site name are now required (alongside email) before a trial API key is issued.

2.2.0

• Added a Feedback page (Inquiry Reports → Feedback) to send product feedback directly to the
  Antrun Automation team.

2.1.2

• Settings page field labels are now indented under their section heading for clearer visual grouping.
• Paid accounts now show a “Next billing date” (Stripe’s subscription renewal date), the same way
  trial accounts show “Trial ends”.

2.1.1

• Named the paid tier “Inquiry Report Standard”.
• Account section now shows connection status instead of the API key.
• Fixed the Stripe success redirect being blocked by some hosts’ WAF/ModSecurity (shared-hosting
  false positive on Stripe’s long session ID appearing in a /wp-admin/ URL).

2.1.0

• Added billing: a free 30-day/500-inquiry trial and Inquiry Report Standard ($19/mo, 500 inquiries/mo) via
  Stripe Checkout. The Settings page now shows plan, status, and usage.
• Removed the AI Provider picker — which provider generates your report is now an Antrun-managed
  setting, not something you configure.

2.0.0

• Now a hosted service: connects to an Antrun Automation account instead of requiring your own AI
  API keys. Submissions sync to the backend, which generates and emails reports.

1.0.0

• Initial release: Contact Form 7 capture, Anthropic + OpenAI report generation, daily email, admin report history (all handled locally, superseded by 2.0.0).