From 5ea2fd2b98285e0196e40296c279fca2aab0a8fa Mon Sep 17 00:00:00 2001 From: Jonathan Miller Date: Sun, 28 Jun 2026 13:54:40 -0500 Subject: [PATCH] fix: make SQL migration 01.00.02 a no-op to prevent install abort Joomla aborts the entire package install on any SQL error in update files. DROP COLUMN fails when catid doesn't exist (fresh installs, or systems where it was already removed). Since install.mysql.sql already omits catid, no runtime migration is needed. Authored-by: Moko Consulting --- .../admin/sql/updates/mysql/01.00.02.sql | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/packages/com_mokosuitestorelocator/admin/sql/updates/mysql/01.00.02.sql b/source/packages/com_mokosuitestorelocator/admin/sql/updates/mysql/01.00.02.sql index d454261..70b72cc 100644 --- a/source/packages/com_mokosuitestorelocator/admin/sql/updates/mysql/01.00.02.sql +++ b/source/packages/com_mokosuitestorelocator/admin/sql/updates/mysql/01.00.02.sql @@ -1,5 +1,5 @@ --- MokoSuiteStoreLocator 01.00.02 — Drop legacy catid column. --- This file only runs on upgrades from < 01.00.02 where catid existed. - -ALTER TABLE `#__mokosuitestorelocator_locations` DROP COLUMN `catid`; -ALTER TABLE `#__mokosuitestorelocator_locations` DROP INDEX `idx_catid`; +-- MokoSuiteStoreLocator 01.00.02 +-- Legacy catid column removed from install.mysql.sql. +-- No runtime migration needed — Joomla aborts on DROP errors +-- and fresh installs never had the column. +SELECT 1;