Changelog Demando Pro

Changelog für das verfügbaren WooCommerce-Plugin Demando Pro: Updates, Korrekturen und Funktionsentwicklung.

v1.0.13

The plugin description, the readme and the admin strings still named the free plugin by its old name in places the rename missed. They now all read Demando.
The Polish translation is complete again. Regenerating the template exposed strings that had never been translated, because the old template did not contain them at all.

v1.0.12

Renamed to Demando Pro. The free plugin it extends was renamed to Demando for the WordPress.org directory, which asks a plugin name to lead with a distinctive coined word rather than a generic one, and the paid add-on now carries the same name. The text domain, the stored options and every hook are unchanged, so nothing on an existing install moves.

v1.0.11

Fixed: the erasure screen repeated the "some product enquiries could not be deleted" notice once for every request the erasure took. WordPress asks the eraser for one batch at a time and joins the messages of all of them without removing duplicates, and the enquiries that refuse to delete are met again by every request. Measured on one seeded set of 2000 enquiries, alternating one blocked and one deletable: the erasure took 71 requests and printed the notice 71 times. It now prints once, and the same run still removes all 1000 deletable enquiries.
Fixed: the translation template named version 1.0.9 and pointed the erasure notice at a source line the string had moved away from. Translation tools read those references to show a string in its context.

v1.0.10

Fixed: an erasure request gave up as soon as one full batch of 100 enquiries refused to delete, even when deletable enquiries sat behind them. Measured on one seeded set, 100 blocked enquiries in front of 60 deletable ones: 1.0.9 removed 0 in a single request and reported 100 retained, 1.0.8 removed 60 across two requests. The request now walks past the rows it could not delete and carries on, removing all 60 in one request and reporting the 100 blocked ones as retained. A batch nothing can delete still ends the request once nothing is left behind it, so an undeletable enquiry cannot be selected forever.
Fixed: a trashed enquiry was invisible to both the personal data export and the erasure while still holding the name, email address and message. The query asked for post status "any", which WordPress expands to every status not flagged exclude_from_search, and Trash carries that flag. The Enquiry Log has a Trash view, so a trashed enquiry is something an administrator can produce from the admin screen. Both requests now name every registered status, and an ordered offset replaces page numbers so a set the deletion itself changes cannot be skipped over.

v1.0.9

Fixed: a personal data erasure request stopped after the first 100 enquiries and reported itself complete. The eraser asked for page two of the same query it had just deleted page one of, so it looked past everything that survived. A customer with more than 100 logged enquiries kept their name, email address and message in the database while WordPress showed the erasure as done. Every batch now restarts at the top of what is left instead of stepping past it.
Changed: enquiries that could not be deleted, because another plugin blocked the deletion, are now counted as retained and reported with a message on the erasure screen. They were previously counted as neither removed nor retained, which read as success.

v1.0.8

Fixed: arrow glyphs in the admin menu paths, and in the strings handed to translators. An arrow inside a translatable string makes the glyph every translator's problem and changes the layout in any locale that drops it.

v1.0.7

The translation template was regenerated. It still named an older version of the plugin and pointed at source lines that had since moved, which is what translation tools read to show a string in context.

v1.0.6

Fixed: the auto-reply subject and body were English sentences in the packaged defaults, so they never reached the .pot and could not be translated. Activation wrote them into the database, which froze the English in place: a shop running in Polish emailed English however complete the language pack was. Both are now translatable, and a stored value that is byte for byte the old English default is cleared on upgrade so the translation takes over. Wording a merchant typed themselves is left alone.
Fixed: clearing the subject or message field on the settings screen put the English default straight back on save, so there was no way to fall back to the translated wording. An empty field now stays empty and uses the translated default, shown in the field as a placeholder.

v1.0.5

Fixed: the plugin title label on Freemius notices rendered white on a background measuring 2.37:1, where WCAG AA wants 4.5:1 for text that size. The label now uses the same grey WordPress core uses, at 4.61:1.
Fixed: the public key constant was defined inside the guard for the product id constant, so it would have gone undefined if anything had defined the id first. Harmless today, wrong the moment it is not.

v1.0.4

Fix: deleting the plugin now removes its options and transients instead of leaving them in the database, on every site of a network. The free plugin's own settings are untouched.

v1.0.2

v1.0.1

v0.5.1

Renamed plugin slug and text domain to `plogins-enquire-pro` for consistency across the Plogins family. No feature changes.

v0.5.0

Branded HTML email templates for store-owner notifications and shopper auto-replies via `HtmlEmails`, `enquire/mail_args` and `enquire_pro_autoreply_args`.
HTML settings on **WooCommerce > Demando Pro** (accent colour, logo URL, per-audience toggles).

v0.4.0

Recipient routing: route store-owner enquiry emails by product ID, category ID or vendor user ID via `enquire/mail_args`.
Routing rules UI on **WooCommerce > Demando Pro** (up to 15 rules, first match wins).

v0.3.0

v0.2.0

Adds **enquiry log**, private CPT under WooCommerce with product, contact details and message for each submission (hooks `enquire/enquiry_sent`).
Renames settings screen to **WooCommerce > Demando Pro** with toggles for logging and auto-reply.

v0.1.0

First release. Adds the **auto-reply confirmation email** feature on top of the PRO add-on bootstrap.