From Aimeos documentation

Revision as of 12:23, 2 April 2015 by Aimeos (talk | contribs)


<translate> Aimeos is extremely configurable and most of the things can be changed, replaced or adapted. Thus, there are a lot of configuration options available. This pages tries to categorize the available options and gives an introduction to the different areas.

Some configuration options are relevant for shop owners but most of them are useful for developers. The links below contain a listing of all available options for each target audience:

Please have a look at the documentation specific to the application you are using to find out how you can set the configuration options properly:

The sections below divide the configuration options into different areas they apply for.


The list of frontend related configuration options consists of the options available in the "HTML clients" and the frontend controllers. The HTML clients are responsible for generating the HTML code that is sent to the browser. The frontend controllers process the incoming requests using the given parameters and providing data to the HTML clients.

Developers can replace every used class by their own implementation. To use the new class, it's name must be added to the configuration so it will be instantiated:


There are some things a shop has to do regularly to work properly like sending confirmation e-mails, decrease the stock level of products bought and so on. These scheduler tasks are called job controllers in the Aimeos context. Their implementations can be exchanged as well when configuring different class names.

Administration interface

The default administration interface is build on the ExtJS Javascript library and allows editors to manage all types of shop related content. The ExtJS interface itself displays the available content and enables editors to add, delete and edit content. The controllers are responsible for processing the change requests and to hand the changed data to the MShop library for storing it. The controllers can be exchanged by different implementations when configuring different class names.