ENPLDEES
Volver a Klepsidro Prov1.0.12 (18 versiones)

Changelog Klepsidro Pro

Changelog del plugin de WooCommerce Klepsidro Pro (disponible): actualizaciones, correcciones y desarrollo de funciones.

v1.0.12
  • 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 Klepsidro.
  • 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.11
  • Renamed to Klepsidro Pro. The free plugin it extends was renamed to Klepsidro 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.10
  • Fixed: the countdown recorded nothing at all on a shop that had never opened the Ticker settings screen, which is most of them. The check that an event only counts while the countdown is enabled read the raw `ticker_settings` option, and that option does not exist until the screen is saved once: the free plugin merges its packaged defaults, where the countdown ships enabled, so the countdown rendered on the product page while every one of its beacons came back 403. The check now reads the setting through the same two steps the renderer does, so the enabled countdown is the counted countdown. Unticking Enable still stops the counting. Numbers on the analytics screen start from the first visit after this update; the traffic before it was not stored anywhere and cannot be recovered.
v1.0.9
  • Fixed: a copy of the old counts that stopped part of the way through was recorded as done. The database version was stamped whether or not the copy finished, and that stamp is the first thing every later request checks, so a refused chunk was never retried and the counts in it were lost rather than repeated. Driven against a real database with the copy's INSERT refused: nothing copied and the migration called applied, where the next request now finishes it and records it. A shop whose copy failed under 1.0.8 gets the rest of its counts on the first load after this update, the old option was kept.
  • Changed: the note on translations said the package carries no compiled translation files and that WordPress.org language packs deliver them. Neither is true of a plugin that is not in the WordPress.org directory: the Polish, German and Spanish translations ship inside the package, under `languages/`, and nothing else could deliver them. The files stay, the sentence was wrong.
v1.0.8
  • Fixed: every countdown beacon rewrote the whole statistics option. Each event read one option holding all counts for all products, rebuilt it in PHP and wrote it back, so two visitors arriving in the same moment overwrote each other's increment, and nothing capped how many products that option could hold. Counts now live in their own table, one row per product, day and metric, and each event is a single atomic increment of that row. Measured against a real database with eight processes recording twenty-five views each: 200 of 200 counted after the fix, 82 of 200 before it.
  • Fixed: beacons sent with navigator.sendBeacon were rejected with 403. The handler read the nonce only from the X-WP-Nonce header, which a beacon cannot set, while the script puts it in the query string. In every browser that supports sendBeacon, which is every current one, nothing was recorded. Expect the numbers to start rising after this update, from real traffic that was being dropped.
  • Changed: an event is recorded only for an id that is really a product, and only while the countdown is enabled. Both were accepted before, so a forged request could open a row for any number. Correction: this release read the enabled flag straight from the stored option rather than from the merged settings the countdown renders on, so on a shop that had never saved the settings screen it counted the countdown as disabled and recorded nothing. Fixed in 1.0.10.
  • Changed: the analytics screen lists the 100 most viewed products and states how long daily counts are kept. The retention period is unchanged at 90 days. Stores with more than 100 products in the report saw the full list before.
  • Upgrade: counts recorded by 1.0.7 and earlier are copied into the new table on the first load after the update, for the days inside the 90 day retention window. Older days are dropped, as they already were on every write. A copy that is interrupted never adds to what it already wrote. Deleting the plugin now removes the new table as well.
v1.0.7
  • 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.6
  • 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.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
  • Added bundled Polish, German and Spanish translations for the plugin interface.
v1.0.1
  • First stable release.
v0.5.2
  • Plugin Check: escaping/sanitisation/i18n/hygiene fixes.
v0.5.1
  • Renamed plugin slug and text domain to `plogins-ticker-pro` for consistency with the Plogins family.
v0.5.0
  • Countdown analytics: views and add-to-cart counts per product on WooCommerce > Klepsidro Analytics (`CountdownTracker` REST beacon).
v0.4.0
  • Product targeting by ID, category or tag on WooCommerce > Klepsidro (`PlacementRules` + `ticker/active`).
v0.3.0
  • Recurring weekly and monthly countdown windows globally and per product (`RecurringWindowResolver`).
  • Between windows the countdown is hidden instead of showing an expired message.
v0.2.0
  • Scheduled campaign start windows globally and per product (`ScheduleValidator`, `GlobalSchedule`).
  • Per-product campaign end dates via `ticker/end_timestamp` (`CampaignResolver`).
v0.1.0
  • Initial release: per-product campaign end date field that drives the free plugin's countdown.
Volver a Klepsidro ProPrecios