ENPLDEES
Volver a Shiplume Prov1.0.15 (20 versiones)

Changelog Shiplume Pro

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

v1.0.15
  • Bar analytics now count a threshold reached after the cart or checkout updates. The tracker listened with native addEventListener for events WooCommerce fires through jQuery, so it never heard them and only counted what was on the page at load.
v1.0.14
  • Display name follows the free plugin: Shiplume Pro - Shipping Progress Bar for WooCommerce.
v1.0.13
  • Renamed to Shiplume Pro, following the free plugin, and it now declares the free plugin under its new wordpress.org slug, shiplume. Settings and licence are unchanged.
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 Shiplume.
  • 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 Instigo Pro. The free plugin it extends was renamed to Instigo 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 bar recorded nothing at all on a shop that had never opened the Nudge settings screen, which is most of them. The check that an event only counts while the bar is enabled read the raw `nudge_settings` option, and that option does not exist until the screen is saved once: the free plugin merges its packaged defaults, where the bar ships enabled, so the bar rendered on the cart and checkout 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 bar is the counted bar. 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 bar event rewrote the whole statistics option. Each beacon read one option holding all counts for all placements, 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 large that option could grow. Counts now live in their own table, one row per placement, day and metric, and each event is a single atomic increment of that row. Measured against a real database with twelve processes recording forty views each: 480 of 480 counted after the fix, 138 and 147 on two runs before it.
  • Fixed: analytics 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, so 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 a placement the bar can actually render in (cart, checkout, inside totals, floating) and only while the bar is enabled. Both were accepted before, so a forged request could open a row for any string. Filter `nudge_pro_analytics_placements` to add one. Correction: this release read the enabled flag straight from the stored option rather than from the merged settings the bar renders on, so on a shop that had never saved the settings screen it counted the bar as disabled and recorded nothing. Fixed in 1.0.10.
  • Changed: the analytics screen states how long daily counts are kept. The retention period is unchanged at 90 days.
  • 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
  • Fixed: the floating bar message and the tier 2 and tier 3 messages were stuck in English on a translated shop. They shipped as plain strings in a config file rather than as translatable strings, so they never reached the translation template and no language pack could replace them.
  • The defaults are now translated strings resolved when the bar is about to be shown, never written back to the database. Wording you typed yourself is still used exactly as you typed it, and the settings screen shows the translated default as the field placeholder.
  • On update, a message left byte for byte as the old English default is cleared so the translated one takes over. Anything you edited, including a hand translation, is matched exactly and kept.
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.4.2
  • Plugin Check: escaping/sanitisation/i18n/hygiene fixes.
v0.4.1
  • Renamed plugin slug and text domain to `plogins-nudge-pro` for consistency across the Plogins family. No functional changes.
v0.4.0
  • Conversion analytics via `BarTracker`, `BarAnalyticsRepository` and **WooCommerce > Shiplume Analytics**. Requires Nudge 0.1.3+.
v0.3.0
  • Tiered reward milestones via `TieredRewards` and `nudge/bar_context`. Configure tier 2/3 goals on **WooCommerce > Shiplume Pro**. Requires Nudge 0.1.2+.
v0.2.0
  • Per-zone free-shipping thresholds via `ZoneThresholds` and a toggle on **WooCommerce > Shiplume Pro**. Requires Nudge 0.1.1+.
v0.1.0
  • Initial release: floating mini-cart free-shipping progress bar (top/bottom, customisable message and colours) and WooCommerce > Shiplume Pro settings screen.
Volver a Shiplume ProPrecios