README

Compatibility

Versions

• versions 7.0.x - compatible with OXID eShop compilation 7.5.x and higher
• versions 6.0.x - compatible with OXID eShop compilation 7.4.x and higher
• versions 5.0.x - compatible with OXID eShop compilation 7.3.x and higher
• versions 4.2.x - compatible with OXID eShop compilation 7.2.x and higher
• versions 4.0.x - 4.1.x - compatible with OXID eShop compilation 7.1.x
• versions 3.x - compatible with OXID eShop compilation 7.0.x
• versions 2.x - compatible with OXID eShop compilation 6.0.x - 6.5.x

Branches

• b-7.6.x is compatible with OXID eShop b-7.6.x branch
• b-7.5.x is compatible with OXID eShop b-7.5.x branch
• b-7.4.x is compatible with OXID eShop b-7.4.x branch
• b-7.3.x is compatible with OXID eShop b-7.3.x branch
• b-7.2.x is compatible with OXID eShop b-7.2.x branch
• b-7.1.x is compatible with OXID eShop b-7.1.x branch, works with Twig engine only from here on
• b-7.0.x is compatible with OXID eShop b-7.0.x branch and supports Legacy Smarty engine
• b-2.x is compatible with OXID eShop compilations: 6.2.x - 6.5.x

Module installation via composer

In order to install the module via composer run one of the following commands in commandline in your shop base directory (where the shop's composer.json file resides).

• composer require ddoe/wysiwyg-editor-module:^7.0.0 to install the released version compatible with OXID eShop v7.6.x
• composer require ddoe/wysiwyg-editor-module:dev-b-7.6.x to install the specific unreleased branch

Module activation in OXID eShop Admin

After installation, please, activate the module in OXID eShop Admin EXTENSIONS -> Modules -> "Summernote WYSIWYG Editor for OXID eShop" -> Activate

Development installation

The installation instructions below are shown for the current SDK for shop 7.6. Make sure your system meets the requirements of the SDK.

1. Ensure all docker containers are down to avoid port conflicts

2. Clone the SDK for the new project

echo MyProject && git clone https://github.com/OXID-eSales/docker-eshop-sdk.git $_ && cd $_

1. Clone the repository to the source directory

git clone --recurse-submodules https://github.com/OXID-eSales/ddoe-wysiwyg-editor-module.git --branch=b-7.6.x ./source

1. Run the recipe to setup the development environment

./source/recipes/setup-development.sh

You should be able to access the shop via

• Frontend http://localhost.local
• Admin Panel: http://localhost.local/admin
  • (credentials: noreply@oxid-esales.com / admin)

Running the tests and quality tools

Check the "scripts" section in the composer.json file for the available commands. Those commands can be executed by connecting to the php container and running the command from there, example:

make php
composer tests-coverage

Commands can be also triggered directly on the container with docker compose, example:

docker compose exec -T php composer tests-coverage

Rebuilding the assets

To rebuild the assets, latest node docker container can be used. The one is pulled automatically if you are using the installation method from the previous section. What is left - connect to the container, install the npm dependencies and run the assets building process

make node

Navigate to the module directory and run:

npm install
npm run build

Alternatively, if you're actively developing and want changes to be applied automatically, you can enable watch mode:

npm run watch

Migration

Besides running the usual migrations process, there are some addition actions that may differ by project.

Media paths to IDs

The command ddoewysiwyg:migrate:urls-to-ids tableName fieldName tableIdKey migrates hardcoded media paths inserted by earlier version of MediaLibrary to Media object ID's. It takes the tableName, fieldName, and the tableIdKey field as params.

Example use:

vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxartextends OXLONGDESC
vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxartextends OXLONGDESC_1
vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxcategories OXDESC
vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxcategories OXDESC_1
vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxcontents OXCONTENT
vendor/bin/oe-console ddoewysiwyg:migrate:urls-to-ids oxcontents OXCONTENT_1

Ensure all fields for which the WYSIWYG editor is used are migrated.

Media alt texts

The command ddoewysiwyg:migrate:alt-texts tableName fieldName tableIdKey adds oeMediaAlt placeholders to media image alt attributes. This enables media alt texts managed in the Media Library to be rendered automatically in the frontend. It should be run after the ddoewysiwyg:migrate:urls-to-ids migration, as it relies on the data-id attribute being present on media image tags.

The command handles the following cases:

• Empty or missing alt attribute: replaced with the oeMediaAlt placeholder
• Already migrated (oeMediaAlt placeholder present): skipped
• Custom alt text written manually: not modified, but listed in the command output for manual review

Example use:

vendor/bin/oe-console ddoewysiwyg:migrate:alt-texts oxartextends OXLONGDESC
vendor/bin/oe-console ddoewysiwyg:migrate:alt-texts oxartextends OXLONGDESC_1
vendor/bin/oe-console ddoewysiwyg:migrate:alt-texts oxcontents OXCONTENT
vendor/bin/oe-console ddoewysiwyg:migrate:alt-texts oxcontents OXCONTENT_1

If any media images have custom alt text, the command will output them:

Warning: The following media images have custom alt text that was NOT modified:

  [OXID=abc123] media-id="68cab835a253c" alt="My product photo"

Please review these entries and update alt texts manually if needed.

Bugs and Issues

If you experience any bugs or issues, please report them in the section WYSIWYG Editor + Media Gallery of https://bugs.oxid-esales.com.