
Place code in a dedicated extensions directory under the shop root, add a PHP file, boot the Oxyd framework, and test a read data by item number function.
Build a SQL statement to retrieve a product id by item number and ensure the product is active and available using the Doctrine Query Builder in the Oxid eShop framework.
Load the product by id and read its language-specific title and price with the active record pattern. Use getprice and getlink for data; the framework handles language, currency, and updates.
Create an Oxford eShop component named Product Data Reader, register its services in the Symphony Di container, enable auto wiring, install the extension, and test it locally.
Build a custom Oxid eShop 7 console command with the product data reader, extending Symfony's command and implementing configure and execute, then register it as a console service.
Create and configure an oxide eShop module by building composer.json and metadata.php, installing assets, and activating the module via the OE console across the four states, including per shop options.
Extend a suitable template block inside a module to add a header banner, by locating the apex header layout block and using twig extends and the parent function.
Extend the shop start controller with a module to provide product details by registering class extensions in metadata, creating a custom controller, and binding template variables for Twig rendering.
Learn how to implement module translations in OXID eShop by moving hard-coded text to translation files, using the translate function and twig templates, and format prices with currency-aware twig extensions.
Create a styles.css file inside assets/css, then include it in the template header using the Ovu config get module URL to apply custom module styles globally.
Configure a new module setting to input an item number, read via the module settings service, and render a product data banner on the shop frontend, in the metadata.php file.
Learn to add an event subscriber to monitor product stock, trigger on after model update, and reset the module setting to hide a promotional banner when stock drops below ten.
The OXID eShop is the toolbox for individual e-commerce solutions. With the extension possibility you can change layout, design and adapt the business workflows to your needs. But how is it done? Start the course and begin with the basics to read and write data. Then learn about the two extension possibilities - component and module - and start to build your own extensions!
Scenario
To implement components you begin by creating a service class. This service is then used to build your custom console command. The module section will teach you how to extend template blocks to introduce your own elements to the OXID eShop. In this course you build a little banner. You will also learn how to style the banner and bring data from the shop to it. Latter one is done by extending given classes. To fulfil the whole module experience you will be teached how to add settings to a module and translate introduced texts. At the end the event mechanism is used to automate a provided scenario where the stock falls below a given number of units.
Goal
After watching all videos you know about the basics of the OXID eShop Framework and will be able to implement components and modules to adapt the shop's behavior or layout and style.