v1.0.1 — Brand de-leak (kvc → vehiclecompat, keystation_ → etechflow_)
[1.0.1] — 2026-06-03 — Brand de-leak: rename Keystation-derived routes, files, and CSS classes
Cosmetic but important release. Renames every customer-visible and
admin-visible identifier that still carried the original developer's
"Keystation Vehicle Compatibility" (kvc) / "Keystation" branding, so the
module ships as a generic eTechFlow product any merchant can install
without seeing another shop's name in their URLs or DevTools.
Changed (customer-facing)
- URL prefix renamed:
frontName="kvc"→frontName="vehiclecompat".
Part Finder page is now at/vehiclecompat/find/indexinstead of
/kvc/find/index. The Options + Tree AJAX endpoints follow:
/vehiclecompat/options/index,/vehiclecompat/tree.json. - Frontend JS file renamed:
view/frontend/web/js/kvc-part-finder.js
→part-finder.js. The Alpine.js function inside is now
vehicleCompatPartFinder()(waskvcPartFinder()), and its store key
is'vehicleCompatSel'(was'kvcSel'). - CSS class prefix:
kvc-*→vc-*across all templates (vc-row,
vc-ico-left,vc-trigger,vc-side,vc-find-page,vc-pager,
vc-cat-chips, etc.). Keeps the prefix short while removing the
Keystation branding. - Frontend layout file:
view/frontend/layout/kvc_find_index.xml→
vehiclecompat_find_index.xml. - Block names in layout XML:
kvc.sidebar.summary/
kvc.category.filter.chips→vehiclecompat.sidebar.summary/
vehiclecompat.category.filter.chips.
Changed (admin-facing)
- 11 admin layout + UI component files renamed from
keystation_vehicle_*toetechflow_vehicle_*so they match the
module's existing admin route id (etechflow_vehicle). Previously
they were dead-code on disk (route id and file name didn't match;
Magento auto-loads layout by URL pattern). Renaming gets them back
on the auto-load path under the canonical eTechFlow naming.
Added
Setup/Patch/Data/V101ReleaseMarker.php— no-op release marker
patch. Continues the always-a-patch discipline. Depends on the three
v1.0.0 data patches so patches run in version order.
Breaking changes ⚠
Anyone who installed v1.0.0 in the ~1 hour between v1.0.0 and v1.0.1
publication will see the Part Finder URL change. No real customers
were installed at the time of this release. Bookmarks pointing at
/kvc/find/index will 404 — clients should update to
/vehiclecompat/find/index.
If you've embedded the Part Finder form in CMS blocks or themes via
JavaScript, the Alpine.js function call needs renaming:
kvcPartFinder() → vehicleCompatPartFinder(). Same for any
Alpine.store('kvcSel') references.
Why this exists
The original developer of this module built it first for the Keystation
brand and then handed the code to eTechFlow. The brand prefixes
(kvc/, keystation_vehicle_*) survived the rebadge. v1.0.0 shipped
with that leak. v1.0.1 cleans it up so the module sells generically.
Migration
composer require etechflow/module-vehicle-compat:^1.0.1
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flushPre-flight check after upgrade:
SELECT module, schema_version, data_version FROM setup_module
WHERE module='ETechFlow_VehicleCompat';Both columns should read 1.0.1. If data_version is stale, re-run
setup:upgrade — do NOT flush cache yet.
After upgrade, the Part Finder page is at /vehiclecompat/find/index.
A merchant who wants to preserve the old /kvc/* URLs can ship a
custom URL rewrite from /kvc/* to /vehiclecompat/* in their web
server config — but a fresh install no longer publishes any /kvc/*
URLs at all.