Ubercart — Drupal 6 and 7 legacy commerce
Ubercart was Drupal's original shop system, and real shops still run on it. BOA carries both its generations on maintained, security-patched legacy cores — most hosts stopped offering this era of Drupal years ago; here it's a supported, deliberate capability.
UC7 — Ubercart on Drupal 7
Ubercart 3 assembled on BOA's enhanced Drupal 7 core, with the classic companion module set (Views, Rules, Pathauto and friends) already in the build. This platform installs and serves on current servers — verified on a stock modern box — so an existing D7 shop can be imported, cloned and kept trading with the full panel workflow.
UC6 — Ubercart on Drupal 6 / Pressflow
Ubercart 2 on BOA's Pressflow-based Drupal 6 LTS core. One precondition: the Drupal 6 era installer needs an older PHP generation on the server, and current servers ship modern PHP only — so if this platform won't build or install, ask your host to enable the legacy PHP package. Server-side switch, quickly done.
Why this exists — and the way out
Carrying D6/D7 commerce isn't nostalgia; it's the runway. A shop that keeps trading today can move when it suits the business, not when a host's platform sunset forces it — and the moves are panel tasks, not projects you improvise:
- Toward modern Commerce: the current
Commerce Kickstart platform (
CK3) lives on the same server; rebuild there, clone-verify, cut over. - The D6 → D7 → Backdrop chain: Drupal 6 sites can travel to Drupal 7 and on to Backdrop CMS entirely through panel tasks — the Backdrop topic covers both upgrade paths, working on a copy while the original keeps serving.
Good to know
- Legacy platforms get the same nightly backups, HTTPS renewal and caching as everything else — age doesn't demote a site here.
- Old shops attract old exploits; BOA's hardening and web application protections sit in front of these sites exactly as for current ones — see Protecting your site.
Where to go next
- Choosing and managing platforms
— getting
UC7/UC6into your platform list.