Tagged: vendor customizations
Pages with this tag
Implement Customizations
1Add custom features to a CodeCanyon Laravel app without losing them on the next vendor update — the ZajModules + vendor-customizations system.
1 · The decision rule
2Three questions that route any change to the right update-safe home — a ZajModule package, the vendor-customizations overlay, or a _zaj migration that adds marked columns to a vendor table — so nothing you build is lost on the next vendor update.
3 · Vendor customizations
3When a vendor file must be edited, store the edited copy in the resources/vendor-customizations/ overlay that mirrors vendor paths, mark your changes with ZAJ:BEGIN/END markers, and re-apply the overlay after every composer install overwrites vendor/.
4 · Track and restore
4Keep a MOD-NNN tracking log and a _CUSTOMIZATIONS file documenting every vendor patch, and run restore-vendor-customizations.php to re-apply your overlay automatically after composer install or a vendor update overwrites vendor/.
3 · Restore customizations
5Re-apply your vendor-customizations overlay with the restore script after the clean vendor/ rebuild, re-scan for backdoor signatures, confirm every ZajModule, zajm_ table, and _zaj column survived untouched, verify the patches behaviourally, then deploy staging-first.
Laravel/CodeCanyon — Handbook
6The mental models behind running a CodeCanyon Laravel app — when a change is a module vs a customization, where admin files live, how to extend the schema safely, and how to version your fork.
ZajModules vs customizations
7The core mental model — deciding whether a change is a new ZajModule, a vendor customization, or a schema extension, and why that split keeps your app update-safe.
Customization decision
8The one-screen routing for any change to a CodeCanyon Laravel app — vendor file edit → vendor-customizations overlay, new functionality → ZajModule, vendor-table column → additive _zaj migration — so nothing is lost on the next vendor update.
Gotchas
9The CodeCanyon Laravel traps that bite — per-environment APP_KEY, APP_DEBUG off the box, the utf8mb4 schema, the vendor overlay that composer install reverts, secrets in server sync, and Cloudflare Full (Strict) SSL — each with the one-line fix.
Laravel/CodeCanyon — Kits
10Reusable, copy-paste bundles for CodeCanyon Laravel work — like the vendor-customization restore script that re-applies your overlay after composer install.
Vendor-customization restore kit
11The restore-vendor-customizations.php script — re-applies your resources/vendor-customizations/ overlay after composer install or a vendor update reverts vendor/ to vanilla, honoring your ZAJ:BEGIN/END markers.