OXID eShop Extension for Supporting more fields in oxOrderArticles
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Application
docs/img
CHANGELOG.md
LICENSE.md
README.md
composer.json
jxorderfields.png
metadata.php

README.md

jxOrderFields

OXID eShop Extension for Supporting more fields in oxOrderArticles

OXID eShop Versions

The module is available for the following versions

  • OXID eShop 6 (actual module version)
  • OXID eShop 4.x / 5.x (download here)

Setup

OXID eShop 6

  1. Install the module
    composer config repo.JxMods/JxOrderFields git https://github.com/job953/jxorderfields.git

    composer require jxmods/jxorderfields

  2. Activate the module
    Navigate in the admin backend of the shop to Extensions - Modules.
    Select the module jxOrderFields and click on Activate.

If you open the menu Products, you will see the the new menu item Text Finder.

  1. First switch to the tab Settings and enter these fields (one in each line) from oxarticles you want to transfer additionally to oxorderarticles on each sale and save the settings. Activate the module now.
    The fields, defined in the settings, will be created in the table oxorderarticles during the module activation if they don't exist. To avoid conflicts, the prefix ox will be removed and replaced by the prefix jx.
    If you later add more fields to the settings, you have to Deactivate the module once and Activate it again for checking and creating the new database fields.

  2. As an alternative method to the automatically created fields, you can create the additional database fields in the table oxorderarticles manually, but with the prefix jx instead of ox.

OXID eShop 4/5

Goto branch oxid-4x and follow the instructions there.

Examples

oxorder.oxean --> oxorderarticles.jxean
oxorder.oxvendorid --> oxorderarticles.jxvendorid

Hints

  • Later changes (eg. larger field size) made on the original fields will be not handled by the module.
  • Removing fields from the definition doesn't delete the fields in oxorder
  • The activation events works as well for the built-in fields as for custom fields.

Screenshots

tbd ...