errorHandle – AI Website Assistant

Rejestr zmian

0.2.10

A fix for the commonest question this plugin exists to answer.

• „My website is slow. What is causing it?” works again. The plan
  validator was throwing away good plans. Asked that question, the model
  reliably returned a complete, valid plan — a summary, a read-only
  diagnosis step, sensible notes — while labelling its own intent
  „clarify” and leaving the question blank. Taking that label at its word
  meant discarding the plan and showing an error instead. A plan that
  asks a question and supplies steps has contradicted itself, and the
  steps are the substance, so the steps now win.
• An empty plan now returns a clear 422 rather than a 500, and says so in
  words you can act on instead of a stack trace.

Nothing else changed. No new capabilities, no database changes, no
settings to revisit.

0.2.9

A check now tells you what it found.

• Findings are listed, not just counted. 0.2.8 would say „found 2
  smaller notes” and never say what they were, which is the one thing
  you asked. Each finding now shows how serious it is, what it is, what
  it means, the measurements behind it, and whether errorHandle can fix
  it for you.
• Severity is written as a word — Serious, Worth attention, Minor,
  Fine — as well as shown in colour, so it reads the same for everyone.
• No more „Undo this” after a check that changed nothing. The button
  now appears only when there is genuinely something to undo.
• The Ask screen invites a problem as readily as a change.

0.2.8

You can now tell errorHandle what is wrong, not only what to change.

• „My website is slow. What is causing it?” now works. So does
  „something is wrong, find the problem” and „check my site’s health”.
  errorHandle investigates and reports what it found.
• The health checks existed in 0.2.5 but only behind a Health tab you
  had to know to open — no use to someone who does not know what is
  wrong and therefore does not know where to look. They are now on the
  end of a sentence.
• Asking about speed gets an answer about speed. Asking about security
  gets an answer about security.
• Looking changes nothing and costs no credits, so you can ask as
  often as you like, even on an exhausted trial.

0.2.7

Clearer credits, and a fix to when they appeared to refresh.

• Pro now shows when your credits refresh, by name: „Pro — 258
  credits left this month. Your 300 credits refresh on 14 November.”
• Running out is explained properly. You get 300 more on a named
  date, your subscription is not affected, nothing is cancelled, and you
  are not charged again for the refresh.
• Fixed a stale balance. The monthly refresh only happened when you
  next ran a command, so after the month turned the plugin could still
  show nothing left until you tried to use it. The refresh was real; the
  number on screen was out of date. Reading your balance now gives the
  same answer as spending from it.
• A trial shows no refresh date, because ten commands are for the
  lifetime of the site rather than a monthly allowance.

0.2.6

Fixes the Upgrade button, which did not work in 0.2.5.

• The Upgrade and Manage subscription buttons sent you to the wrong
  place. The plugin was handing the browser the address of its own API
  instead of the Stripe page, so pressing Upgrade appeared to do nothing.
  Found by running the whole purchase on a real site rather than trusting
  that the request succeeded — it did succeed; the answer was simply read
  wrongly.
• The allowance now reports credits, so a Pro site reads „258 credits left
  this month” rather than counting in free commands it no longer has.

0.2.5

errorHandle Pro is available.

• Pro: $9 a month or $90 a year, for 300 credits a month with no API
  key to manage. Buy it, and cancel it, from your own dashboard — payment
  is handled by Stripe and errorHandle never sees your card.
• A credit is one thing you asked for and applied. Everything errorHandle
  does today costs one credit; more involved work will cost more, and you
  are always told before it starts.
• Nothing that was free has become paid. The ten free commands, your
  own API key with no metering, the offline planner and every capability
  are exactly as they were.
• Added a Health screen: nine read-only checks over your site — updates,
  unsupported PHP, overdue scheduled tasks, unmaintained plugins, debug
  settings left on, and data loading on every page. Scans are free, make
  no external request, and never cost a credit.
• Two repairs you can approve from a finding: stop an oversized leftover
  setting loading on every page (exactly reversible), and clear expired
  temporary data (which cannot be undone, and says so).

0.2.4

Plainer wording and a shorter preview, for people who do not think in
WordPress terms.

• The Ask screen now says „What would you like errorHandle to do?” and
  explains what happens next: errorHandle shows you the plan and asks for
  your approval.
• The buttons say what they do: Preview changes, Test changes,
  Approve changes. „Build it”, „Test it” and „Apply” are gone.
• A much shorter preview. It leads with how many pages are affected and
  what the change actually is. The page-by-page list — eleven rows for an
  eleven-page change — now folds behind „Show all 11 pages this affects”.
  Nothing is hidden from you; it is one click away, and warnings are still
  shown in full and never folded.
• The Ask box empties once a request has been applied, so the next one
  starts clean. A draft you have typed but not submitted, or a plan you have
  previewed or tested but not approved, is left exactly as you left it.
• Rewrote the plugin description around what errorHandle actually does for
  you: Ask, Preview, Approve, Done, with real examples. It is about 40%
  shorter, and the technical detail about AI providers moved into the FAQ.
• New screenshots following one real change from request to result.
• Correction: the previous description said errorHandle could change
  site „settings”. It cannot, and never could — there is no such operation.
  The FAQ now lists exactly what it can change.

0.2.3

Ownership and licensing, stated plainly. No functional change.

• errorHandle is developed and operated by errorHandle LLC. The plugin
  header, this readme, the website and the portal now say so consistently.
• Added the standard GPL copyright notice to the plugin file, which was
  missing.
• A new „Who makes this” section separates the two things that carry the
  errorHandle name: this plugin is GPLv2-or-later and always will be,
  and the optional hosted AI service is a separate proprietary service.
  Nothing about the service limits your rights to the plugin.
• No „all rights reserved” notice appears on the plugin, and none will.
  Under the GPL those rights are granted to you, not reserved.

0.2.2

• Fixed a privacy label that could call a reused plan „cached” when it had
  been generated fresh, and vice versa.
• Clearer wording throughout the approval and simulation screens.

0.2.1

• Simplified the whole interface for non-technical administrators.
• Fixed the Ask box not clearing after a request was submitted.
• Proper mobile layout for every screen.

0.2.0

• First public release on WordPress.org.
• Removed the ability to store or run CSS and JavaScript, along with several
  other changes requested in plugin review.

0.1.0

• Initial private beta.