Upgrading from Wheels 3.x — the honest map #2655
bpamiri
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just published a new post on blog.wheels.dev walking the 3.x → 4.0 upgrade as it surfaced for a real production codebase: https://blog.wheels.dev/upgrading-from-wheels-3x
What it covers
wheels snippets→wheels generate snippets,redirectTo()scope tightening on Lucee 7,testbox→wheelstestnamespace, tests directory rename (functions/→functional/), RocketUnit removed from core, CORS default flip (wildcard → deny-all),allowEnvironmentSwitchViaUrloff in prod + reload password required.application.wireboxor thewirebox.system.ioc.Injectorclass path, so apps that bootstrap WireBox inApplication.cfc(the canonical 2.x pattern) must rewrite that file before first boot, adapter or no adapter.rewrite.config404s static assets in non-standard directories (/miscellaneous/,/javascripts/,/stylesheets/,/files/)reloadPassword=...in.envdoes not satisfy the framework's empty-check; must wire viaset(reloadPassword=env("WHEELS_RELOAD_PASSWORD"))inconfig/settings.cfmlib/ext/if you came from CommandBoxlibDirsInvalidClassExceptionbeforeonrequeststart.cfmruns — the AppSerial kill-switch cannot fire; one-time fix is to truncate the session-storage table after cutoverv4.0.1 heads-up
Most of the "things that bite at boot" are already being addressed in the forthcoming v4.0.1 — improved CLI defaults for
rewrite.config, expandedwheels upgrade checkcoverage, and clarified canonical-guide docs onreloadPasswordand the adapter's WireBox limits. A follow-up post will land when v4.0.1 ships, pointing back to this one for the lived-experience context.Where to read more
If you are mid-upgrade and the post does not cover something you hit, please share — the audit trail is most useful when it is complete.
Beta Was this translation helpful? Give feedback.
All reactions