Historia zmian Lokilo Pro

Historia zmian dostępnej wtyczki Lokilo Pro: aktualizacje, poprawki i rozwój funkcji dla WooCommerce.

v1.0.13

The plugin now declares the free plugin under its wordpress.org slug, lokilo. It named "locator", which no installed plugin carries, so WordPress refused to activate it next to Lokilo.

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 Lokilo.
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 Lokilo Pro. The free plugin it extends was renamed to Lokilo 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 map hydrated every published store on every page that shows it, then dropped the ones with no coordinates. A shop that had geocoded twenty of four hundred locations paid for four hundred to draw twenty pins. The shortcode now asks the database for published stores that have both coordinates filled in, 500 of them by default, and `[locator_map limit="-1"]` still places every one. `locator/map_limit` moves the default.

v1.0.9

Fixed: the CSV store import read the whole upload into memory and created every store inside one admin request. Reading 5,000 rows from a 1.06 MB file held 4.9 MB of PHP memory before the first store was written, and a file long enough to exhaust max_execution_time died mid-loop with no report on screen, having silently created part of itself. The file is now read as a stream, so the same 5,000 rows grow memory by 47 KB, and one request imports at most 500 rows or 60 percent of max_execution_time, whichever comes first.
Added: "Start at line" on the import screen. When a pass stops early the notice names the line it stopped at and the field is pre-filled with it, so uploading the same file again imports the rest. A row with a blank store_id creates a store every time it runs, so the notice also says not to start earlier than the line shown. The two bounds are filterable: locator/import_max_rows and locator/import_time_budget.
Fixed: the import report listed one line per problem row, so a bad file could outgrow the transient it is stored in. It now lists the first 50 and counts the rest.

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

Removed a setting that controlled nothing. `locator_pro_map_enabled` was written to your database every time the plugin was activated, no screen ever offered it and no code ever read it, so it could not switch the map on or off. The map is opt-in already: it appears where you place the `[locator_map]` shortcode and nowhere else. The leftover row is removed on update.

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

v1.0.1

v0.3.1

Maintenance: plugin slug and text domain renamed to `plogins-locator-pro` for consistency across the Plogins family. No functional changes.

v0.3.0

CSV bulk import of store locations via `StoreImporter` and the free `StoreWriter` service. Settings on **WooCommerce > Lokilo Import**.
Requires Locator 0.1.2 or later for `locator/import_store_fields` and `locator/store_imported`.

v0.2.0

Region grouping on the `[locator]` storefront list: per-store Region (Pro) field, toggle under WooCommerce > Lokilo (Pro). Requires Locator 0.1.1+.

v0.1.0

Initial release. Boots on top of the free Lokilo plugin via the `locator/booted` action, verifies the free plugin and minimum version, wires premium services/hooks into the shared container, declares WooCommerce HPOS + Blocks compatibility, integrates the Freemius SDK, and ships the `[locator_map]` interactive map view (Leaflet + OpenStreetMap, no API key).