netgen/ezplatform-sylius

eZ Platform distribution coupled with Sylius eCommerce

Installs: 5

Dependents: 0

Suggesters: 0

Security: 0

Stars: 32

Watchers: 11

Forks: 11

Open Issues: 1

Language:Shell

Type:project

dev-master / 2.5.x-dev 2019-08-23 13:39 UTC

This package is auto-updated.

Last update: 2024-11-24 21:17:54 UTC


README

This is a proof of concept integration of eZ Platform & Sylius eCommerce. eZ Platform being a really good CMS, and Sylius being a really good eCommerce solution, both running on Symfony full stack framework, and considering the fact that there is no quality solution that does both CMS and eCommerce right, it is only natural to try and connect the two.

Here both, eZ Platform and Sylius, run on same Symfony full stack instance. A bundle exists to assist the integration, by implementing custom user providers that make it possible to connect the users together.

Sylius users act as primary users, while eZ Platform users are secondary, you can use them (if they're connected to Sylius users) or not, it's up to you. However, you will at least need one Sylius admin user to be connected to one eZ Platform admin user in order to enable seamless login to both admin panels.

Limitations

Due to way Sylius users are implemented, it is currently not possible to be logged in with both Sylius admin and Sylius shop users. Use a second browser or incognito mode to login both ways. Hopefully, this will be solved by the time this integration reaches a stable release.

Installation instructions

Run the following instructions to install the integration. This will first install Sylius, then install eZ Platform, and finally connect the admin users from Sylius and eZ Platform together.

IMPORTANT

Always make sure your default locale is compatible with default locale from your eZ Platform database. app/config/config.yml file sets the default locale to en_GB due to eng-GB (which is converted internally to en_GB) being the default locale in eZ Platform clean data.

Due to how Sylius install process works and the fact that this integration requires additional database tables, you first need to create the database schema and then run Sylius install command. Due to this, when asked by Sylius install command, DO NOT drop and create the database and its schema (meaning, answer the first two questions NO).

$ git clone https://github.com/netgen/ezplatform-sylius.git
$ cd ezplatform-sylius
$ composer install
$ php bin/console --env=prod doctrine:schema:create
$ php bin/console --env=prod sylius:install
$ php bin/console --env=prod ezplatform:install clean
$ php bin/console --env=prod assetic:dump
$ php bin/console --env=prod assets:install --relative --symlink
$ php bin/console --env=prod ezsylius:user:connect

To connect the users, when asked, select the admin Sylius user type, then enter the e-mail address of Sylius admin user (the one you specified while running sylius:install command), then enter the username of eZ Platform admin user (usually admin).

Once all this is done, you will need to generate assets for Sylius frontend and backend interfaces. You need yarn installed for this. Once installed, to generate the assets, run the following from the project root:

$ yarn install
$ yarn build

eZ Publish legacy administration

When installing and activating eZ Publish legacy administration interface, be sure to activate the EzSyliusBundle after EzPublishLegacyBundle.

To activate support for Sylius Product field type in legacy administration interface, activate ezsylius legacy extension in your INI files, regenerate legacy autoloads and clear legacy caches.

Access the eZ Platform admin interface

eZ Platform admin interface is available in standard /admin route. Use the Sylius admin username and password to login.

Access the Sylius shop and Sylius admin interface

If you didn't change any parameters while running composer install, Sylius shop will be available at /shop, while Sylius admin interface will be available at /sylius/admin/. If you don't like these paths, you can change them in app/config/sylius_parameters.yml.