PHPackages                             melisplatform/melis-demo-commerce - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Admin Panels](/categories/admin)
4. /
5. melisplatform/melis-demo-commerce

ActiveMelisplatform-module[Admin Panels](/categories/admin)

melisplatform/melis-demo-commerce
=================================

Official Melis Platform Demo Site

v5.3.1(3w ago)114OSL-3.0PHPPHP ^8.1|^8.3

Since Oct 28Pushed 3w ago5 watchersCompare

[ Source](https://github.com/melisplatform/melis-demo-commerce)[ Packagist](https://packagist.org/packages/melisplatform/melis-demo-commerce)[ Docs](https://github.com/melisplatform/melis-demo-commerce)[ RSS](/packages/melisplatform-melis-demo-commerce/feed)WikiDiscussions master Synced today

READMEChangelog (4)Dependencies (12)Versions (19)Used By (0)

Melis Demo Commerce
===================

[](#melis-demo-commerce)

> **Module:** `melisplatform/melis-demo-commerce` · **Namespace:** `MelisDemoCommerce` · `melis-site: true` · `melis-module-category: commerce`**Audience:** end users · developers · AI agents **What it is:** a ready-made demo e-commerce storefront **site** for MelisPlatform (the commerce counterpart of `melis-demo-cms`) — a full front office (catalog, product/variant pages, cart, multi-step checkout, account, orders) plus a one-time setup wizard that seeds a complete demo catalog (products, variants, categories, attributes, prices, stock, a coupon and sample clients/orders). Built on the `melis-commerce` engine.

---

A ready-made demo e-commerce **site** for the [Melis Platform](https://www.melistechnology.com/). It is the commerce counterpart of `melis-demo-cms`: a full storefront (catalog, product/variant pages, cart, checkout, account, orders) plus a seeded demo catalog (products, variants, categories, attributes, prices, stock, a coupon, and sample clients/orders).

This module is a *site* module — it is referenced from `vendor/` and registered with the platform, then its demo data is installed through a one-time **setup wizard**.

---

Requirements
------------

[](#requirements)

Before installing this module you need a **working Melis Platform** with:

- PHP **8.1** or **8.3**
- A platform already installed (database created, the `melis_core_platform` row present, and the DbDeploy migrations run). Visiting `/melis` should give you a working back office.
- The **MelisCommerce** engine installed and its DbDeploy run, so the `melis_ecom_*` tables and the commerce reference data (countries, currencies, commerce languages, attribute types, document types) already exist.
- These dependency modules installed (pulled automatically by Composer): `melis-commerce`, `melis-cms`, `melis-cms-slider`, `melis-cms-prospects`, `melis-cms-news`, `melis-cms-page-script-editor`.

> The setup wizard **adds a new site** to your platform. It does not overwrite existing sites, and it resolves all database IDs at runtime — so it can be installed onto a platform that already hosts other sites (e.g. the CMS demo).

---

How the install works (in short)
--------------------------------

[](#how-the-install-works-in-short)

1. Composer places the module in `vendor/melisplatform/melis-demo-commerce` and records its `extra.module-name` so the platform can find it.
2. You register the module so the platform loads it.
3. You open `/MelisDemoCommerce/setup` on a domain that is **not yet bound to another site**.
4. The wizard runs 15 steps, creating the site, pages, templates, sliders, news, the commerce catalog (attributes → products → categories → variants → prices → stock), a coupon and sample clients/orders. Unknown IDs are resolved as rows are inserted and written back into the site's generated config files (the `[:token]` placeholders in `config/*.dist`).

---

Manual installation
-------------------

[](#manual-installation)

### 1. Get the module with Composer

[](#1-get-the-module-with-composer)

If it is already listed in your project's `composer.json`, just install dependencies:

```
composer install
```

Otherwise add it:

```
composer require melisplatform/melis-demo-commerce
```

If you edited the module after installing (e.g. pulled a branch), refresh Composer's autoload so the `Module` class and namespace map are picked up:

```
composer dump-autoload
```

### 2. Register the module's path with the platform

[](#2-register-the-modules-path-with-the-platform)

This is a **site** module — it is loaded for its own front domain through the vhost's `MELIS_MODULE` env (step 4), **not** through the back-office module list.

> ⚠️ **Do NOT add `MelisDemoCommerce` to `config/melis.module.load.php`.** That file is the **back-office** module list; adding a site module there makes the platform treat every `/MelisDemoCommerce/*` URL as a back-office request and redirect it to `/melis/login`, so the setup wizard becomes unreachable.

The module only needs to be in the **path map** so the platform can locate it. Add it to `config/melis.modules.path.php`:

```
'MelisDemoCommerce' => '/vendor/melisplatform/melis-demo-commerce',
```

(Or simply delete `config/melis.modules.path.php` — it is regenerated on the next request from the installed packages, picking up this module via its `composer.json` `extra.module-name`.) Then clear the platform cache:

```
rm -rf cache/meliscore_platform_cache-* cache/config/*
```

### 3. Make the required paths writable

[](#3-make-the-required-paths-writable)

The wizard copies product/category images and writes the site's generated config files, so these must be writable by the web server:

- `public/media/` (the wizard creates `public/media/commerce/` inside it)
- `vendor/melisplatform/melis-demo-commerce/config/` (it generates `module.config.php`, `melis.plugins.config.php` and `MelisDemoCommerce.config.php` from the `*.dist` templates)

### 4. Set up a domain / virtual host

[](#4-set-up-a-domain--virtual-host)

Point a virtual host at the project's `public/` directory using a domain that is **not already used by another site** on this platform (the front engine routes by domain — a domain bound to another site will intercept `/MelisDemoCommerce/setup`). Declare the platform and this module via env vars:

```

    DocumentRoot "/path/to/project/public"
    ServerName www.mycommerce.local

        Options -Indexes +FollowSymLinks +ExecCGI
        DirectoryIndex index.php
        AllowOverride All
        Require all granted

    SetEnv MELIS_PLATFORM "local"            # your platform/environment name
    SetEnv MELIS_MODULE   "MelisDemoCommerce"

```

Add the domain to your hosts file:

```
127.0.0.1   www.mycommerce.local

```

Restart/reload the web server.

### 5. Run the setup wizard

[](#5-run-the-setup-wizard)

Open:

```
http://www.mycommerce.local/MelisDemoCommerce/setup

```

Fill in:

- **Protocol** – `http` or `https`
- **Site Domain** – the domain you just configured (e.g. `www.mycommerce.local`)
- **Site Label** – a display name (e.g. `My Commerce Site`)

Click **Start setup**. The wizard runs these steps automatically (the *products* and *variants*steps are large and take longest — let it finish):

`site → templates → pages → sliders → news → prospects_theme → document_types → attributes → product_text_types → products → categories → variants → coupons → client_and_orders → setup_main_page`

When you see **“MelisDemoCommerce setup completed.”** the install is done.

### 6. Verify

[](#6-verify)

Browse to `http://www.mycommerce.local/` — you should see the demo storefront with categories, products and prices.

---

Re-running the install
----------------------

[](#re-running-the-install)

Each run regenerates the site's config files from the `*.dist` templates, but it does **not** delete data it previously inserted — re-running on the same database will create duplicate rows. To start over cleanly, restore the database to its pre-install state first, then run the wizard again.

---

Troubleshooting
---------------

[](#troubleshooting)

SymptomCause / fix`/MelisDemoCommerce/setup` redirects to `/melis/login``MelisDemoCommerce` was added to `config/melis.module.load.php` (the back-office list) — remove it. A site module is loaded via the vhost's `MELIS_MODULE`, not that list.Blank page / 404 at `/MelisDemoCommerce/setup`The domain is already bound to another site (use an unbound domain), or `MELIS_MODULE` isn't set on the vhost. Clear `cache/`.`Access permission denied … make … writable`Make `public/media/` and the module's `config/` directory writable.`Current Platform "" has no data on database``MELIS_PLATFORM` isn't set for this vhost, or the platform isn't installed. Set `SetEnv MELIS_PLATFORM`.Module won't initialize / class not foundRun `composer dump-autoload`.Setup stops on `client_and_orders``MELIS_MODULE` isn't set for the vhost — add `SetEnv MELIS_MODULE "MelisDemoCommerce"`.---

Support
-------

[](#support)

- Email:
- Source:

###  Health Score

44

—

FairBetter than 90% of packages

Maintenance68

Regular maintenance activity

Popularity7

Limited adoption so far

Community14

Small or concentrated contributor base

Maturity77

Established project with proven stability

 Bus Factor1

Top contributor holds 57.4% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~166 days

Total

6

Last Release

22d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/f8c3d1de854682cd37de2faa73a026b1c83b4b15500f352077581948c5d778ce?d=identicon)[melisplatform](/maintainers/melisplatform)

---

Top Contributors

[![rbbrioso28](https://avatars.githubusercontent.com/u/9497212?v=4)](https://github.com/rbbrioso28 "rbbrioso28 (112 commits)")[![sircxes](https://avatars.githubusercontent.com/u/21098160?v=4)](https://github.com/sircxes "sircxes (49 commits)")[![fparan](https://avatars.githubusercontent.com/u/39509647?v=4)](https://github.com/fparan "fparan (25 commits)")[![sgris](https://avatars.githubusercontent.com/u/3981660?v=4)](https://github.com/sgris "sgris (6 commits)")[![simonalcover](https://avatars.githubusercontent.com/u/17284664?v=4)](https://github.com/simonalcover "simonalcover (3 commits)")

---

Tags

cmsmodulezf2melis

### Embed Badge

![Health badge](/badges/melisplatform-melis-demo-commerce/health.svg)

```
[![Health](https://phpackages.com/badges/melisplatform-melis-demo-commerce/health.svg)](https://phpackages.com/packages/melisplatform-melis-demo-commerce)
```

###  Alternatives

[melisplatform/melis-cms

Melis Platform CMS module

115.7k25](/packages/melisplatform-melis-cms)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
