- Is offline/oc-mall-plugin a Laravel package or an October CMS plugin?
- It is an October CMS plugin, not a conventional Laravel package. It registers through a Plugin.php bootstrapper and ships backend controllers, settings models, and Twig-rendered CMS components such as mallProduct, cart, and checkout. It uses Laravel as its underlying framework, so the patterns feel familiar, but you cannot drop it into a standalone Laravel application.
- How do I install offline/oc-mall-plugin?
- Install it through Composer or the October CMS marketplace, then run php artisan october:migrate to create the commerce tables. Store administration is largely configuration in the October backend, and a demo theme is available as a reference for front-end wiring. Plan extra effort for payment and shipping adapters rather than expecting a configure-and-go setup.
- Does oc-mall-plugin work with standalone Laravel or a headless JavaScript front end?
- No, not cleanly. The commerce domain is coupled to October's backend controllers, settings models, and CMS components, so there is no straightforward extraction path into standalone Laravel, Symfony, or a headless stack. Adopting Mall effectively means adopting October CMS as your application shell, so it is a poor fit if headless is a requirement now or within two years.
- Which October CMS and PHP versions does Mall support?
- The plugin targets October CMS 3.x running on PHP 8.1 or 8.2, typically with MySQL or Postgres and Redis for cache and sessions. However, the last release was June 2022, so its pinned dependency set predates current October 3.x branches and PHP 8.2+ hardening. Run an install spike on your exact versions before committing to the platform.
- Is offline/oc-mall-plugin still actively maintained?
- The last release was June 2022, and stewardship is concentrated with a single vendor, OFFLINE GmbH, with a small community of around 174 GitHub stars and zero Packagist dependents. That dependents figure is a weak signal because October plugins are commonly installed via the marketplace or VCS, but it still does not indicate a thriving ecosystem. The MIT license means forking is legally clean and viable if your team accepts ownership.
- How do I integrate Stripe or PayPal payments with October CMS Mall?
- Payments route through Omnipay, so you add or author a gateway class and configure it in the Mall backend. Because the plugin has not shipped since 2022, several Omnipay gateways, notably Stripe and PayPal, have deprecated older API versions in that window, so expect to update or write gateway classes. Confirm a maintained Omnipay gateway exists for each provider you are contractually required to support.
- How hard is migrating an existing store to oc-mall-plugin?
- Data migration is a bespoke exercise and typically the single largest line item. You need to map product and variant schemas, migrate customer credentials, import order history, and set up URL redirects from the old platform. Budget for this separately from installation and theme work, and validate it in a spike before committing.
- Does Mall support multi-currency, multi-store, and tax jurisdictions?
- Mall ships a full commerce domain including catalog, variants, categories, properties, carts, orders, payment and shipping methods, taxes, currencies, discounts, and wishlists. The open question is whether its model covers your specific multi-currency, multi-store, and tax-jurisdiction requirements without patching core. Validate those requirements in a spike, since core patches raise upgrade costs on an already stale dependency set.
- How do I customize the storefront theme in oc-mall-plugin?
- Front-end work is Twig partials and wiring Mall's CMS components, such as mallProduct, cart, checkout, and order lookups, into your existing theme. A demo theme is available as a reference, and most admin behavior is configuration rather than code. Real development effort usually lands in custom payment and shipping adapters, not in the storefront markup.
- How do I test an October CMS Mall store?
- Testing is constrained because commerce logic is entangled with October's backend controllers and CMS components, which limits isolated unit testing of the domain. Unit-test your own gateway and shipping adapters in isolation, and use October's testing helpers with a seeded test database for cart and checkout flows. End-to-end tests through the Twig storefront are the practical way to cover the checkout path.