Zurück zu Respondo Prov1.0.12 (18 Releases)

Changelog Respondo Pro

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

v1.0.12
  • Security (low): FAQ votes are capped at 30 per visitor address per hour. The one-vote-per-answer lock includes the browser's User-Agent, so a script rotating it could inflate the helpful counts without limit. The lock now lasts 30 days instead of a year, so it no longer fills the options table for twelve months.
v1.0.11
  • 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 Respondo.
  • 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.10
  • Renamed to Respondo Pro. The free plugin it extends was renamed to Respondo 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.9
  • 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.8
  • Fixed: FAQ votes disappeared into silence. The tally was rendered into a paragraph that was always hidden and the server had always returned both numbers, but nothing ever displayed them. After voting, the shopper now sees how many people found that answer helpful.
v1.0.7
  • The translation template was regenerated. 60 strings added to the plugin since the template was last built were missing from it, so no translator could reach them in any language, and 4 strings the plugin no longer uses have been dropped. Nothing you see changes; what a translator can see does.
v1.0.6
  • 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.5
  • 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.4
  • Declared compatibility with WooCommerce 10.9.
  • Copy: replaced long dashes with plain punctuation across the interface.
  • Housekeeping: corrected the Last-Translator header in the bundled catalogues.
v1.0.3
  • Added the AI Act article 50 disclosure label for AI-generated answers, so a shopper can tell which answers were written by a model.
v1.0.2
  • Added bundled Polish, German and Spanish translations for the plugin interface.
v1.0.1
  • First stable release.
v0.4.2
  • Plugin Check: escaping/sanitisation/i18n/hygiene fixes.
v0.4.1
  • Renamed plugin slug and text domain to `plogins-answers-pro` for consistency across the Plogins family. No feature changes.
v0.4.0
  • AI FAQ drafting (`FaqAiDraft`, `AiDraftClient`) on the product FAQs tab with OpenAI-compatible API settings.
  • Drafts insert into the repeater for merchant review; nothing publishes until the product is saved.
v0.3.0
  • FAQ categories via `FaqCategories`: merchant-defined labels, per-product assignment, storefront category filter pills (combines with live search).
  • Requires Answers 0.1.2+ for optional `category` on FAQ items and repeater hooks.
v0.2.0
  • FAQ helpful/not-helpful voting via `FaqVoting` and `answers/faq_after_answer`.
  • Requires Answers 0.1.1+ for stable FAQ keys and render hooks.
v0.1.0
  • Initial release: live FAQ search filter for the product FAQ accordion.