Zurück zu Lokilov1.2.6 (28 Releases)

Changelog Lokilo

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

v1.2.6
  • Search now matches store names, cities and addresses with non-ASCII capitals (Łódź, Überlingen). The storefront box and the list-stores ability lower-cased only A to Z, so these stores never matched.
  • The read-only abilities are now flagged read-only where the Abilities API looks for it, so they are called with GET as the API expects for read-only abilities (GET used to return 405 and only POST worked). list-stores and get-directory-settings also accept a call with no input.
  • The list-stores ability searches every store before applying its limit, so a store past the first page can be found.
  • The get-store ability loads only the store it was asked for.
v1.2.5
  • The upgrade notice's "Coming soon" and "Get notified" labels are English source strings for every language; Polish sites used to get their own Polish source text, which translators in other languages then saw untranslated.
v1.2.4
  • The PRO upsell pointed at a screen called "Store Locator Import". The paid add-on renames that screen to Lokilo Import, so the instruction named a menu entry that is not there.
v1.2.3
  • Fixed: the PRO promo card on the settings screen still told merchants to use `[locator]`, the shortcode the previous release replaced, so it was handing out an instruction that no longer works.
v1.2.2
  • The shortcode is now `[lokilo]`. It used to be `[locator]`, a tag generic enough that any other plugin could claim it first, and which no longer matched the plugin's name. This is the last release in which that could change without breaking existing pages, because the plugin had not been published yet.
  • The WooCommerce submenu now reads Lokilo rather than Store Locator, and the places the documentation still said Locator were updated.
v1.2.1
  • The sidebar upgrade promo now follows the same dismissal as the banner. Dismissing the banner used to leave a full-height advert on the settings screen for good, which is not what the WordPress.org guideline on upgrade prompts means by used with moderation.
v1.2.0
  • Renamed to Lokilo. The WordPress.org review team asks a plugin name to lead with a distinctive, coined identifier rather than a generic descriptive word. Lokilo is Esperanto for a locating tool. The text domain follows the name; the stored locations, the settings, the [locator] shortcode and every hook are unchanged.
v1.1.9
  • Fixed: the directory announced how many locations it had printed, not how many the shop has. Since 1.1.8 the page renders 200 by default, so a shop with 700 locations told every visitor, and read out to every screen reader, "200 locations". The count now reads "Showing 200 of 700 locations", and a shop whose locations all fit on the page reads exactly as before.
  • Fixed: the search box only ever looked through the locations printed on the page, and nothing said so. A visitor searching for the 500th location was told "No locations match your search" and given no reason. The page now states above the list that it is showing the first 200 of 700 and that search covers only those, and the empty result says it again.
v1.1.8
  • Fixed: the directory rendered every published store on the page. The shortcode ignored its attributes entirely, so there was no way to ask for fewer, and a shop with a long franchise list built every store, and a separate photo lookup per store, into one public page. `[locator]` now renders 200 stores and honours `limit`, including `limit="-1"` for all of them, and the store photos are primed in one pass for the whole page instead of a lookup per store.
v1.1.7
  • Fixed: the PRO upgrade promo kept selling to people who had already bought the paid edition. Only the banner could be dismissed, so the sidebar promo and the locked feature cards followed a paying customer around for good. The promo now checks whether the paid edition is active and steps aside when it is.
  • 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.1.6
  • Fixed: deleting the plugin left the per-user "dismiss" flag from the PRO notice in the database. Uninstall now removes it for every user, not just the one who dismissed it.
v1.1.5
  • 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.1.4
  • Renamed to Plogins Locator - Store Locator for WooCommerce so the name leads with the brand rather than a generic word, which is what the WordPress.org plugin review team asks for. The plugin slug is unchanged.
v1.1.3
  • Removed the "Tested up to" header from the main PHP file. It belongs in readme.txt only, where it is already declared; present in both, the header can override the readme and show a compatibility version that was never intended.
v1.1.2
  • Tested against WordPress 7.1. Verified by activating this build on a clean 7.1 install with WooCommerce 11.1, not by editing the header.
v1.1.1
  • Fixed the PRO promo on the settings screen quoting a price in PLN. PRO is priced and charged in EUR, so an admin on a Polish site was shown a zloty amount and then billed in euro, and the zloty figure was a fixed conversion that drifted from the real charge as the rate moved. The promo now shows the euro price that is actually taken.
v1.1.0
  • An AI assistant working in your wp-admin can now read your store locations for you, through the WordPress Abilities API (WordPress 6.9 and later). Ask it for the shop in a given city or postcode and it reads back the address, phone, email and opening hours, exactly what the storefront search box would find. It can also tell you how the directory is set up.
  • Reading only. Nothing an assistant can call adds, edits or removes a location; that stays in your hands. Only users who can manage WooCommerce can use these, and on WordPress 6.8 and earlier nothing changes.
v1.0.7
  • The store email you type on a location now appears on its card, as a click-to-write link beside the phone number. Until now it was saved and never shown to shoppers.
  • The featured image you set on a location now appears at the top of its card.
  • The text you write in the location editor now appears under the store name.
  • Photo, description and email each get their own switch under WooCommerce > Store Locator, alongside the address, opening hours and phone switches.
v1.0.6
  • Internal: the store-list search builds its meta-key list through an explicitly typed map, so static analysis can see that only strings reach the query. No change in behaviour.
v1.0.4
  • Translations: completed Polish, German and Spanish for the PRO upgrade panel.
v1.0.3
  • Fixed low-contrast admin headings under an OS dark-mode preference.
v1.0.2
  • Added bundled Polish, German and Spanish translations for the plugin interface.
v1.0.1
  • First stable release.
v0.1.4
  • Renamed to Plogins Locator for WooCommerce for a more distinctive plugin name.
v0.1.3
  • Fix: store locations no longer take over the `manage_woocommerce` capability. Registering the locations post type mapped meta caps onto `manage_woocommerce`, which made every `manage_woocommerce` check fail while the plugin was active, hiding the whole WooCommerce admin menu (Settings, Status, Orders) and the plugin's own settings page.
v0.1.2
  • Programmatic store import via `StoreWriter` with `locator/import_store_fields` filter and `locator/store_imported` action.
v0.1.1
  • Add `locator/store_groups` filter so add-ons can group the storefront directory by region or country.
v0.1.0
  • Initial release: store-location post type, [locator] shortcode, searchable list, settings.