v1.7.5

= 1.7.5 =

• Fixed: updating two of these extensions one after the other could fail on the second with "up to date" until Check for updates was pressed again. WordPress rebuilds its update list after each update by asking wordpress.org first, and gives up on the whole list when that call is slow; the plugin now keeps its own update in the list regardless.
• Changed: a release found more than an hour ago is refreshed in the background whenever the Plugins screen is opened, so the newest release is offered rather than an intermediate one.
• New: a Check for updates bulk action on the Plugins screen, which checks every selected extension in one go, and the row that says Updating no longer shrinks on phones.

v1.7.4

1.7.4

Changed

• On the settings tab the help icon now sits directly after each label, and its tooltip opens to the right at full width instead of being cut into a narrow strip to the left. The same placement is used across every extension in this family.

v1.7.3

1.7.3

• Changed - internal formatting only. Some explanatory comments in the settings screen's script were reworded to match the wording used across the rest of these extensions, so the file is easier to compare with its siblings. Nothing about the settings screen, or anything else the plugin does, has changed.

1.7.2

• Fixed - the "Import starter blocklist" buttons rendered on the wrong settings tab. The plugin worked out which tab you were on from the web address, and the address does not name a tab at all when you open Settings from the HivePress menu, so it assumed you were on the Listings tab. That assumption held only while Listings happened to be the first tab in the list, which is not something this plugin controls: with an extension installed whose tab sorts above it, that route put the buttons, and the note beside them, on that other tab, where neither of the boxes they fill exists. The plugin now asks HivePress which settings are actually on the screen, so the buttons appear on the Listings tab and nowhere else, however you got there.

1.7.1

• Changed - the settings screen now carries the same furniture as every other extension in this family. The jump links are labelled "Jump to a section:" and stay with you as you scroll, a Save Changes tab sits on the right edge of the screen wherever you are on the page, and a button in the bottom corner takes you back to the top. If you have another of these extensions installed and it has already put one of those on the screen, this plugin leaves it alone, so you always see one of each rather than two.
• Changed - the settings styles and script are fetched on the Listings tab alone, so nothing extra loads on other extensions' settings tabs.
• Changed - the quick links reuse the names WordPress already gives the section headings, so a link or a bookmark to a section keeps working.

1.7.0

• Added - quick links at the top of the settings screen, one for each section, so you can jump straight to Automated Moderation without scrolling, plus a dividing line between sections.
• Improved - the settings tooltips are wider, so they no longer chop every sentence into a thin ribbon, each description has been shortened to the points that matter when configuring, and section descriptions wrap at a readable width instead of running the full width of a wide screen. The full detail on every check remains in this readme.
• No change to what is blocked, held or scored.

v1.6.11

• Fixed - deleting the plugin now also clears the update check's own leftovers and cancels its background update check. Nothing else has changed in this release.

v1.6.10

Fixed

• A photo refused while AI Photo Review is set to "Block submission" now says so in the dashboard. That kind of hold recorded nothing, so the Moderation column read "No score recorded" and the meta box offered a list of innocent explanations, none of them the real one. An admin clearing the pending queue could publish the listing believing moderation had found nothing. Both screens now state that the AI check flagged a photo, the held/approved/rejected pill covers these listings too, and the meta box gives the same approve-or-reject guidance held listings have always had.

No change to what is blocked, held or scored.

v1.6.9

New

• Three new hooks so Notifications for HivePress can tell a vendor their listing is being held, and tell you why: hpalm/listing_held (with the score, the signals, and whether it came from the submission or the later photo check), hpalm/limit_reached and hpalm/submission_blocked.
• An HPALM_VERSION constant, so another plugin can tell this one is installed without loading anything.

No change to what is blocked, held or scored.

Fixed

• Checking for updates no longer holds up an admin page. The check ran while WordPress was building the Plugins screen, so on a site with several of these extensions one page load made one request to GitHub after another and could sit there for many seconds, once, before behaving normally again for hours. The check now runs in the background moments later. Pressing Check for updates still asks GitHub straight away, because you are waiting for that answer.

v1.6.8

Fixed

• Submitting a listing could hang for up to half a minute, and on a busy site that was enough to make the whole site time out for everyone. Photo review sends one request per photo to OpenAI, which downloads each picture itself, and all of that happened while the vendor sat waiting on the submit button. On a six-photo listing it measured 21 seconds at ordinary API speeds and 32 seconds at slow ones. Every submission in progress occupies one of the small number of PHP processes your host gives you, so a handful at once left nothing to serve anybody else and visitors got 504 errors with nothing to connect them to this plugin.
• The photo review time limit was not the limit it claimed. It was checked only before each photo, so the last one could start with a fraction of a second left and then run its own full timeout on top, turning a stated 20 seconds into 32. Each photo is now given only the time actually remaining.

Changed

• Photos are now reviewed in the background, moments after the listing is submitted, instead of during it. Submitting is immediate again. A listing whose photo is refused is held as Pending exactly as before and never appears publicly, so nothing gets past the check that would not have before. The one difference is when the vendor finds out: they are told on review rather than at the moment they press submit.
• The text check, which is quick because it sends no pictures, still runs during submission but now gives up after 3 seconds instead of 8.

Nothing else changes. Your moderation settings, risk scores and held listings are all unaffected.

v1.6.7

Fixed

• Checking for updates no longer reports "Could not reach GitHub" when nothing is wrong. GitHub allows one server only a limited number of anonymous update checks each hour, and that allowance is shared by every plugin on your site and, on shared hosting, by every other site on the same server. Running out of it is ordinary, but it was reported as though your site could not reach GitHub at all. Update checks now read the release from github.com, which sets no such limit, so the message no longer appears. If the limit is ever reached by another route, the notice now says so plainly instead of blaming your connection.
• A failed update check no longer hides an update that is genuinely waiting. The last successful answer is kept until a later check succeeds, so a pending update stays on the Plugins screen instead of vanishing for an hour.

Nothing else changes, and nothing on your site was ever at risk: a failed check only meant WordPress was not offered the update.

v1.6.6

Changed

• The support link on the Plugins screen now reads "Donate" with a star icon, matching every other extension in the range.
• The thank-you line under the settings form has been removed. The "Donate" link on the Plugins screen and in the plugin details popup is the only place the ask appears now, so it never interrupts you while you are configuring moderation.

v1.6.5

The admin screens have been rewritten in plain English. If you are on 1.6.4, update: the Moderation panel used to say things like "Risk score: 65 of 21", which meant nothing.

• Fixed: the Moderation panel said things like "Risk score: 65 of 21", which reads as a fraction with a bigger top than bottom and means nothing. 21 was never a maximum, it is the point at which a listing stops being published. The panel now says the score in points, whether that reached your Risk Threshold, and what actually became of the listing.
• Fixed: a scored listing that you had already approved or rejected showed a bare number and nothing else, so there was no way to tell an approved listing from one still waiting. Every scored listing now carries a plain label: held for review, held then approved, held then rejected, held now a draft, or published as normal. The same labels appear in the Moderation column.
• Fixed: setting a check to "Add to risk score" did nothing at all until a Risk Threshold was entered, and no screen said so. The option now reads "Add to risk score (set a Risk Threshold below first)" until you set one.
• Fixed: "No risk signals were recorded" sounded like a clean bill of health, when it also appears for listings added in the dashboard or by an import, which are never checked at all. It now says which of those it means.
• Improved: the Moderation column showed a bare number under a heading that said only "Moderation". It now reads "65 points", and rows with nothing recorded say so instead of showing a dash.
• Improved: the breakdown now names what was found in plain words ("Another listing has the same title" rather than "Duplicate title") and puts the unit on every line.
• Improved: a held listing now tells you what to do next, including the Quick Edit route for when a required listing field stops you saving from the edit screen.
• Improved: the Moderation panel now says when your Risk Threshold has changed since a listing was scored, rather than quietly quoting the old figure as though it were current.
• Fixed: a vendor who hit the submission limit was told they had reached "the maximum" without being told what it was. The message now names the number.
• Fixed: the refusal shown for a blocked word said "to continue with submitting your listing" even when the vendor was editing a listing they already had.
• Improved: the two AI refusals now say what the check looks for and what to do about it, and the photo one points out that a photo already on the listing can be the cause, not only one just added.
• Fixed: the Disguised Spellings setting claimed accented text is never blocked, which is the opposite of what it does. Blocking "cafe" does also block "café", and the setting now says so.
• Fixed: the note about percent signs was wrong. WordPress removes a percent sign only when the next two characters are digits or the letters a to f, not any two letters or digits.
• Improved: the verified-vendor setting now mentions that it also exempts those vendors from the submission limit, and the submission limit says which listings count towards it.
• Improved: the OpenAI key field now says where to get a key, and that it is only needed if you use the AI checks.
• Improved: plainer wording throughout the settings, with developer terms such as "fingerprint", "leet-speak", "endpoint" and "tier" removed.
• Added: a quiet "buy me a coffee" link at the foot of the settings, on the plugin's row on the Plugins screen, and in its View details popup.