Skip to content

Product

bundle#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/bundle/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/bundle/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/bundle/decorators/global
  • admin/jqadm/product/bundle/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/bundle/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/bundle/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/bundle/decorators/excludes
  • admin/jqadm/product/bundle/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/bundle/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/bundle/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/bundle/decorators/excludes
  • admin/jqadm/product/bundle/decorators/global

name#

Name of the bundle subpart used by the JQAdm product implementation

admin/jqadm/product/bundle/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Bundle\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product bundle section

admin/jqadm/product/bundle/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the bundle subpart for products.

admin/jqadm/product/bundle/template-item = product/item-bundle-standard
  • Default: product/item-bundle-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

category#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/category/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/category/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/category/decorators/global
  • admin/jqadm/product/category/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/category/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/category/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/category/decorators/excludes
  • admin/jqadm/product/category/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/category/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/category/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/category/decorators/excludes
  • admin/jqadm/product/category/decorators/global

name#

Name of the category subpart used by the JQAdm product implementation

admin/jqadm/product/category/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Category\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product category section

admin/jqadm/product/category/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the category subpart for products.

admin/jqadm/product/category/template-item = product/item-category-standard
  • Default: product/item-category-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

characteristic#

attribute/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/characteristic/attribute/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/characteristic/attribute/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/attribute/decorators/global
  • admin/jqadm/product/characteristic/attribute/decorators/local

attribute/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/characteristic/attribute/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/attribute/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/attribute/decorators/excludes
  • admin/jqadm/product/characteristic/attribute/decorators/local

attribute/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/characteristic/attribute/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/attribute/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/attribute/decorators/excludes
  • admin/jqadm/product/characteristic/attribute/decorators/global

attribute/name#

Name of the characteristic/attribute subpart used by the JQAdm product implementation

admin/jqadm/product/characteristic/attribute/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Characteristic\Attribute\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

attribute/standard/subparts#

List of JQAdm sub-clients rendered within the product attribute section

admin/jqadm/product/characteristic/attribute/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

attribute/template-item#

Relative path to the HTML body template of the attribute characteristic subpart for products.

admin/jqadm/product/characteristic/attribute/template-item = product/item-characteristic-attribute-standard
  • Default: product/item-characteristic-attribute-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/characteristic/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/characteristic/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/decorators/global
  • admin/jqadm/product/characteristic/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/characteristic/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/decorators/excludes
  • admin/jqadm/product/characteristic/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/characteristic/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/decorators/excludes
  • admin/jqadm/product/characteristic/decorators/global

hidden/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/characteristic/hidden/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/characteristic/hidden/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/hidden/decorators/global
  • admin/jqadm/product/characteristic/hidden/decorators/local

hidden/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/characteristic/hidden/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/hidden/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/hidden/decorators/excludes
  • admin/jqadm/product/characteristic/hidden/decorators/local

hidden/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/characteristic/hidden/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/hidden/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/hidden/decorators/excludes
  • admin/jqadm/product/characteristic/hidden/decorators/global

hidden/name#

Name of the characteristic/hidden subpart used by the JQAdm product implementation

admin/jqadm/product/characteristic/hidden/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2018.01

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Characteristic\Hidden\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

hidden/standard/subparts#

List of JQAdm sub-clients rendered within the product hidden characteristics section

admin/jqadm/product/characteristic/hidden/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

hidden/template-item#

Relative path to the HTML body template of the hidden characteristic subpart for products.

admin/jqadm/product/characteristic/hidden/template-item = product/item-characteristic-hidden-standard
  • Default: product/item-characteristic-hidden-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

name#

Name of the characteristic subpart used by the JQAdm product implementation

admin/jqadm/product/characteristic/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Characteristic\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/characteristic/property/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/characteristic/property/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/property/decorators/global
  • admin/jqadm/product/characteristic/property/decorators/local

property/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/characteristic/property/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/property/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/property/decorators/excludes
  • admin/jqadm/product/characteristic/property/decorators/local

property/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/characteristic/property/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/property/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/property/decorators/excludes
  • admin/jqadm/product/characteristic/property/decorators/global

property/name#

Name of the characteristic/property subpart used by the JQAdm product implementation

admin/jqadm/product/characteristic/property/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Characteristic\Property\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/standard/subparts#

List of JQAdm sub-clients rendered within the product property section

admin/jqadm/product/characteristic/property/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

property/template-item#

Relative path to the HTML body template of the property characteristic subpart for products.

admin/jqadm/product/characteristic/property/template-item = product/item-characteristic-property-standard
  • Default: product/item-characteristic-property-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

standard/subparts#

List of JQAdm sub-clients rendered within the product characteristic section

admin/jqadm/product/characteristic/standard/subparts = Array
(
    [property] => property
    [variant] => variant
    [attribute] => attribute
    [hidden] => hidden
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the characteristic subpart for products.

admin/jqadm/product/characteristic/template-item = product/item-characteristic-standard
  • Default: product/item-characteristic-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

variant/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/characteristic/variant/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/characteristic/variant/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/variant/decorators/global
  • admin/jqadm/product/characteristic/variant/decorators/local

variant/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/characteristic/variant/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/variant/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/variant/decorators/excludes
  • admin/jqadm/product/characteristic/variant/decorators/local

variant/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/characteristic/variant/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/characteristic/variant/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/characteristic/variant/decorators/excludes
  • admin/jqadm/product/characteristic/variant/decorators/global

variant/name#

Name of the characteristic/variant subpart used by the JQAdm product implementation

admin/jqadm/product/characteristic/variant/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2018.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Characteristic\Variant\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

variant/standard/subparts#

List of JQAdm sub-clients rendered within the product variant characteristics section

admin/jqadm/product/characteristic/variant/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

variant/template-item#

Relative path to the HTML body template of the variant characteristic subpart for products.

admin/jqadm/product/characteristic/variant/template-item = product/item-characteristic-variant-standard
  • Default: product/item-characteristic-variant-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

decorators#

excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/decorators/excludes = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "client/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "client/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/decorators/global
  • admin/jqadm/product/decorators/local

global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/decorators/excludes
  • admin/jqadm/product/decorators/local

local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/decorators/excludes
  • admin/jqadm/product/decorators/global

domains#

List of domain items that should be fetched along with the product

admin/jqadm/product/domains = Array
(
    [attribute] => attribute
    [media] => media
    [media/property] => media/property
    [price] => price
    [price/property] => price/property
    [product] => product
    [product/property] => product/property
    [stock] => Array
        (
            [0] => default
        )

    [text] => text
)
  • Default: Array
  • Type: array - List of domain names
  • Since: 2016.01

If you need to display additional content, you can configure your own list of domains (attribute, media, price, product, text, etc. are domains) whose items are fetched from the storage.

download#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/download/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/download/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/download/decorators/global
  • admin/jqadm/product/download/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/download/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/download/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/download/decorators/excludes
  • admin/jqadm/product/download/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/download/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/download/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/download/decorators/excludes
  • admin/jqadm/product/download/decorators/global

name#

Name of the download subpart used by the JQAdm product implementation

admin/jqadm/product/download/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Download\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product download section

admin/jqadm/product/download/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.03

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the download subpart for products.

admin/jqadm/product/download/template-item = product/item-download-standard
  • Default: product/item-download-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

fields#

List of product columns that should be displayed in the list view

admin/jqadm/product/fields = Array
(
    [0] => image
    [1] => product.id
    [2] => product.status
    [3] => product.type
    [4] => product.code
    [5] => product.label
)
  • Default: Array
  • Type: array - List of field names, i.e. search keys
  • Since: 2016.04

Changes the list of product columns shown by default in the product list view. The columns can be changed by the editor as required within the administraiton interface.

The names of the colums are in fact the search keys defined by the managers, e.g. "product.id" for the product ID.

item#

config/suggest#

List of suggested configuration keys in product item panel

admin/jqadm/product/item/config/suggest = Array
(
    [0] => css-class
)
  • Default: Array
  • Type: string - List of suggested config keys
  • Since: 2017.10

Product items can store arbitrary key value pairs. This setting gives editors a hint which config keys are available and are used in the templates.

See also:

  • admin/jqadm/catalog/item/config/suggest

media/config/suggest#

List of suggested configuration keys in product media panel

admin/jqadm/product/item/media/config/suggest = Array
(
)
  • Default: Array
  • Type: string - List of suggested config keys
  • Since: 2020.01

Item references can store arbitrary key value pairs. This setting gives editors a hint which config keys are available and are used in the templates.

Number of sub-part links in the product sidebar shown by default

admin/jqadm/product/item/navbar-limit = 7
  • Default: 7
  • Type: integer - Number of product sub-part links
  • Since: 2020.10

The navigation sidebar is divided into the basic and advanced section. All sub-parts up to the configured limit are always shown while additional links in the advanced section are hidden by default. Using this setting you can change how many links are always shown.

See also:

  • admin/jqadm/navbar-limit

price/config/suggest#

List of suggested configuration keys in product price panel

admin/jqadm/product/item/price/config/suggest = Array
(
)
  • Default: Array
  • Type: string - List of suggested config keys
  • Since: 2020.01

Item references can store arbitrary key value pairs. This setting gives editors a hint which config keys are available and are used in the templates.

text/config/suggest#

List of suggested configuration keys in product text panel

admin/jqadm/product/item/text/config/suggest = Array
(
)
  • Default: Array
  • Type: string - List of suggested config keys
  • Since: 2020.01

Item references can store arbitrary key value pairs. This setting gives editors a hint which config keys are available and are used in the templates.

media#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/media/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/media/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/decorators/global
  • admin/jqadm/product/media/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/media/decorators/global = Array
(
    [0] => Invalid
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/media/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/decorators/excludes
  • admin/jqadm/product/media/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/media/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/media/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/decorators/excludes
  • admin/jqadm/product/media/decorators/global

name#

Name of the media subpart used by the JQAdm product implementation

admin/jqadm/product/media/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Media\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/media/property/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2018.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/media/property/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/property/decorators/global
  • admin/jqadm/product/media/property/decorators/local

property/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/media/property/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2018.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/media/property/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/property/decorators/excludes
  • admin/jqadm/product/media/property/decorators/local

property/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/media/property/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2018.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/media/property/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/media/property/decorators/excludes
  • admin/jqadm/product/media/property/decorators/global

property/name#

Name of the property subpart used by the JQAdm product media implementation

admin/jqadm/product/media/property/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2018.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Media\Property\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/standard/subparts#

List of JQAdm sub-clients rendered within the product media property section

admin/jqadm/product/media/property/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2018.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

property/template-item#

Relative path to the HTML body template of the media subpart for products.

admin/jqadm/product/media/property/template-item = product/item-media-property-standard
  • Default: product/item-media-property-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

standard/subparts#

List of JQAdm sub-clients rendered within the product media section

admin/jqadm/product/media/standard/subparts = Array
(
    [property] => property
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2017.07

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the media subpart for products.

admin/jqadm/product/media/template-item = product/item-media-standard
  • Default: product/item-media-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2017.07

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

name#

Class name of the used account favorite client implementation

admin/jqadm/product/name = Standard
  • Default: Standard
  • Type: string - Last part of the class name
  • Since: 2016.01

Each default admin client can be replace by an alternative imlementation. To use this implementation, you have to set the last part of the class name as configuration value so the client factory knows which class it has to instantiate.

For example, if the name of the default class is

 \Aimeos\Admin\JQAdm\Product\Standard

and you want to replace it with your own version named

 \Aimeos\Admin\JQAdm\Product\Myfavorite

then you have to set the this configuration option:

 admin/jqadm/product/name = Myfavorite

The value is the last part of your own class name and it's case sensitive, so take care that the configuration value is exactly named like the last part of the class name.

The allowed characters of the class name are A-Z, a-z and 0-9. No other characters are possible! You should always start the last part of the class name with an upper case character and continue only with lower case characters or numbers. Avoid chamel case names like "MyFavorite"!

option#

config/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/option/config/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/option/config/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/config/decorators/global
  • admin/jqadm/product/option/config/decorators/local

config/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/option/config/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/config/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/config/decorators/excludes
  • admin/jqadm/product/option/config/decorators/local

config/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/option/config/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/config/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/config/decorators/excludes
  • admin/jqadm/product/option/config/decorators/global

config/name#

Name of the option/config subpart used by the JQAdm product implementation

admin/jqadm/product/option/config/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.03

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Option\Config\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

config/standard/exclude#

List of attribute types that shouldn't be managed by the product options client

admin/jqadm/product/option/config/standard/exclude = Array
(
    [interval] => interval
)
  • Default: Array
  • Type: array - List of excluded attribute types
  • Since: 2020.04

If certain attribute types which are referenced using the "config" list type will be managed by other clients, this setting excludes the attribute items from being added and removed by the product config client.

See also:

  • admin/jqadm/product/option/custom/standard/exclude

config/standard/subparts#

List of JQAdm sub-clients rendered within the product config section

admin/jqadm/product/option/config/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2017.03

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

config/template-item#

Relative path to the HTML body template of the config option subpart for products.

admin/jqadm/product/option/config/template-item = product/item-option-config-standard
  • Default: product/item-option-config-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2017.03

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

custom/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/option/custom/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/option/custom/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/custom/decorators/global
  • admin/jqadm/product/option/custom/decorators/local

custom/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/option/custom/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/custom/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/custom/decorators/excludes
  • admin/jqadm/product/option/custom/decorators/local

custom/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/option/custom/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/custom/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/custom/decorators/excludes
  • admin/jqadm/product/option/custom/decorators/global

custom/name#

Name of the option/custom subpart used by the JQAdm product implementation

admin/jqadm/product/option/custom/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.03

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Option\Custom\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

custom/standard/exclude#

List of attribute types that shouldn't be managed by the product options client

admin/jqadm/product/option/custom/standard/exclude = Array
(
    [price] => price
)
  • Default: Array
  • Type: array - List of excluded attribute types
  • Since: 2020.04

If certain attribute types which are referenced using the "custom" list type will be managed by other clients, this setting excludes the attribute items from being added and removed by the product custom client.

See also:

  • admin/jqadm/product/option/custom/standard/exclude

custom/standard/subparts#

List of JQAdm sub-clients rendered within the product custom section

admin/jqadm/product/option/custom/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2017.03

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

custom/template-item#

Relative path to the HTML body template of the custom option subpart for products.

admin/jqadm/product/option/custom/template-item = product/item-option-custom-standard
  • Default: product/item-option-custom-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2017.03

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/option/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/option/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/decorators/global
  • admin/jqadm/product/option/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/option/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/decorators/excludes
  • admin/jqadm/product/option/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/option/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.03

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/option/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/option/decorators/excludes
  • admin/jqadm/product/option/decorators/global

name#

Name of the option subpart used by the JQAdm product implementation

admin/jqadm/product/option/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.03

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Option\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product option section

admin/jqadm/product/option/standard/subparts = Array
(
    [config] => config
    [custom] => custom
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2017.03

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the option subpart for products.

admin/jqadm/product/option/template-item = product/item-option-standard
  • Default: product/item-option-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2017.03

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

order#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/order/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/order/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

@order Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/order/decorators/global
  • admin/jqadm/product/order/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/order/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/order/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

@order Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/order/decorators/excludes
  • admin/jqadm/product/order/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/order/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/order/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

@order Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/order/decorators/excludes
  • admin/jqadm/product/order/decorators/global

fields#

List of list and order columns that should be displayed in the product order view

admin/jqadm/product/order/fields = Array
(
    [0] => order.base.id
    [1] => order.base.currencyid
    [2] => order.base.price
    [3] => order.base.address.firstname
    [4] => order.base.address.lastname
    [5] => order.base.address.city
)
  • Default: Array
  • Type: array - List of field names, i.e. search keys
  • Since: 2019.10

Changes the list of list and order columns shown by default in the product order view. The columns can be changed by the editor as required within the administraiton interface.

The names of the colums are in fact the search keys defined by the managers, e.g. "product.lists.status" for the status value.

name#

Name of the order subpart used by the JQAdm product implementation

admin/jqadm/product/order/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Order\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

@order Developer

standard/subparts#

List of JQAdm sub-clients rendered within the product order section

admin/jqadm/product/order/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

@order Developer

template-item#

Relative path to the HTML body template of the order subpart for products.

admin/jqadm/product/order/template-item = product/item-order-standard
  • Default: product/item-order-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

@order Developer

physical#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/physical/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/physical/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/physical/decorators/global
  • admin/jqadm/product/physical/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/physical/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/physical/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/physical/decorators/excludes
  • admin/jqadm/product/physical/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/physical/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/physical/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/physical/decorators/excludes
  • admin/jqadm/product/physical/decorators/global

name#

Name of the physical subpart used by the JQAdm product implementation

admin/jqadm/product/physical/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Physical\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product physical section

admin/jqadm/product/physical/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the physical subpart for products.

admin/jqadm/product/physical/template-item = product/item-physical-standard
  • Default: product/item-physical-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

price#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/price/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/price/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/decorators/global
  • admin/jqadm/product/price/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/price/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/price/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/decorators/excludes
  • admin/jqadm/product/price/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/price/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/price/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/decorators/excludes
  • admin/jqadm/product/price/decorators/global

name#

Name of the price subpart used by the JQAdm product implementation

admin/jqadm/product/price/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Price\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/price/property/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2019.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/price/property/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/property/decorators/global
  • admin/jqadm/product/price/property/decorators/local

property/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/price/property/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2019.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/price/property/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/property/decorators/excludes
  • admin/jqadm/product/price/property/decorators/local

property/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/price/property/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2019.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/price/property/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/price/property/decorators/excludes
  • admin/jqadm/product/price/property/decorators/global

property/name#

Name of the property subpart used by the JQAdm product price implementation

admin/jqadm/product/price/property/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2019.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Price\Property\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

property/standard/subparts#

List of JQAdm sub-clients rendered within the product price property section

admin/jqadm/product/price/property/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2019.07

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

property/template-item#

Relative path to the HTML body template of the price subpart for products.

admin/jqadm/product/price/property/template-item = product/item-price-property-standard
  • Default: product/item-price-property-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2019.07

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

standard/subparts#

List of JQAdm sub-clients rendered within the product price section

admin/jqadm/product/price/standard/subparts = Array
(
    [property] => property
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the price subpart for products.

admin/jqadm/product/price/template-item = product/item-price-standard
  • Default: product/item-price-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

bought/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/related/bought/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/related/bought/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/bought/decorators/global
  • admin/jqadm/product/related/bought/decorators/local

bought/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/related/bought/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/bought/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/bought/decorators/excludes
  • admin/jqadm/product/related/bought/decorators/local

bought/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/related/bought/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/bought/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/bought/decorators/excludes
  • admin/jqadm/product/related/bought/decorators/global

bought/name#

Name of the related/bought subpart used by the JQAdm product implementation

admin/jqadm/product/related/bought/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Product\Bought\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

bought/standard/subparts#

List of JQAdm sub-clients rendered within the product bought section

admin/jqadm/product/related/bought/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

bought/template-item#

Relative path to the HTML body template of the bought related subpart for products.

admin/jqadm/product/related/bought/template-item = product/item-related-bought-standard
  • Default: product/item-related-bought-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/related/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/related/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/decorators/global
  • admin/jqadm/product/related/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/related/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/decorators/excludes
  • admin/jqadm/product/related/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/related/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/decorators/excludes
  • admin/jqadm/product/related/decorators/global

name#

Name of the related subpart used by the JQAdm product implementation

admin/jqadm/product/related/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.03

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Related\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product related section

admin/jqadm/product/related/standard/subparts = Array
(
    [suggest] => suggest
    [bought] => bought
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

suggest/decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/related/suggest/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/related/suggest/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/suggest/decorators/global
  • admin/jqadm/product/related/suggest/decorators/local

suggest/decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/related/suggest/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/suggest/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/suggest/decorators/excludes
  • admin/jqadm/product/related/suggest/decorators/local

suggest/decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/related/suggest/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/related/suggest/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/related/suggest/decorators/excludes
  • admin/jqadm/product/related/suggest/decorators/global

suggest/name#

Name of the related/suggest subpart used by the JQAdm product implementation

admin/jqadm/product/related/suggest/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2017.07

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Product\Suggest\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

suggest/standard/subparts#

List of JQAdm sub-clients rendered within the product suggest section

admin/jqadm/product/related/suggest/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

suggest/template-item#

Relative path to the HTML body template of the suggest related subpart for products.

admin/jqadm/product/related/suggest/template-item = product/item-related-suggest-standard
  • Default: product/item-related-suggest-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

template-item#

Relative path to the HTML body template of the related subpart for products.

admin/jqadm/product/related/template-item = product/item-related-standard
  • Default: product/item-related-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

selection#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/selection/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/selection/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/selection/decorators/global
  • admin/jqadm/product/selection/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/selection/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/selection/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/selection/decorators/excludes
  • admin/jqadm/product/selection/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/selection/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/selection/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/selection/decorators/excludes
  • admin/jqadm/product/selection/decorators/global

name#

Name of the selection subpart used by the JQAdm product implementation

admin/jqadm/product/selection/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Selection\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product selection section

admin/jqadm/product/selection/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the selection subpart for products.

admin/jqadm/product/selection/template-item = product/item-selection-standard
  • Default: product/item-selection-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

standard#

subparts#

List of JQAdm sub-clients rendered within the product section

admin/jqadm/product/standard/subparts = Array
(
    [selection] => selection
    [bundle] => bundle
    [media] => media
    [text] => text
    [price] => price
    [stock] => stock
    [category] => category
    [characteristic] => characteristic
    [option] => option
    [related] => related
    [supplier] => supplier
    [physical] => physical
    [subscription] => subscription
    [download] => download
    [order] => order
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

stock#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/stock/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/stock/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/stock/decorators/global
  • admin/jqadm/product/stock/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/stock/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/stock/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/stock/decorators/excludes
  • admin/jqadm/product/stock/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/stock/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2016.01

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/stock/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/stock/decorators/excludes
  • admin/jqadm/product/stock/decorators/global

name#

Name of the stock subpart used by the JQAdm product implementation

admin/jqadm/product/stock/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Stock\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product stock section

admin/jqadm/product/stock/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2016.01

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the stock subpart for products.

admin/jqadm/product/stock/template-item = product/item-stock-standard
  • Default: product/item-stock-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

subscription#

decorators/excludes#

Excludes decorators added by the "common" subscription from the product JQAdm client

admin/jqadm/product/subscription/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2018.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This subscription allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/subscription/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/subscription/decorators/global
  • admin/jqadm/product/subscription/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/subscription/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2018.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This subscription allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/subscription/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/subscription/decorators/excludes
  • admin/jqadm/product/subscription/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/subscription/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2018.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This subscription allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/subscription/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/subscription/decorators/excludes
  • admin/jqadm/product/subscription/decorators/global

name#

Name of the subscription subpart used by the JQAdm product implementation

admin/jqadm/product/subscription/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2018.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Subscription\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product subscription section

admin/jqadm/product/subscription/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2018.04

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the subscription subpart for products.

admin/jqadm/product/subscription/template-item = product/item-subscription-standard
  • Default: product/item-subscription-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2018.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

supplier#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/supplier/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2020.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/supplier/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

@supplier Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/supplier/decorators/global
  • admin/jqadm/product/supplier/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/supplier/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2020.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/supplier/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

@supplier Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/supplier/decorators/excludes
  • admin/jqadm/product/supplier/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/supplier/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2020.04

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/supplier/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

@supplier Developer

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/supplier/decorators/excludes
  • admin/jqadm/product/supplier/decorators/global

name#

Name of the supplier subpart used by the JQAdm product implementation

admin/jqadm/product/supplier/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2020.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Supplier\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

@supplier Developer

standard/subparts#

List of JQAdm sub-clients rendered within the product supplier section

admin/jqadm/product/supplier/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2020.04

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

@supplier Developer

template-item#

Relative path to the HTML body template of the supplier subpart for products.

admin/jqadm/product/supplier/template-item = product/item-supplier-standard
  • Default: product/item-supplier-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2020.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

@supplier Developer

template-item#

Relative path to the HTML body template for the product item.

admin/jqadm/product/template-item = product/item-standard
  • Default: product/item-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

template-list#

Relative path to the HTML body template for the product list.

admin/jqadm/product/template-list = product/list-standard
  • Default: product/list-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

text#

decorators/excludes#

Excludes decorators added by the "common" option from the product JQAdm client

admin/jqadm/product/text/decorators/excludes = 
  • Default:
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to remove a decorator added via "admin/jqadm/common/decorators/default" before they are wrapped around the JQAdm client.

 admin/jqadm/product/text/decorators/excludes = array( 'decorator1' )

This would remove the decorator named "decorator1" from the list of common decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") added via "admin/jqadm/common/decorators/default" to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/text/decorators/global
  • admin/jqadm/product/text/decorators/local

decorators/global#

Adds a list of globally available decorators only to the product JQAdm client

admin/jqadm/product/text/decorators/global = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap global decorators ("\Aimeos\Admin\JQAdm\Common\Decorator*") around the JQAdm client.

 admin/jqadm/product/text/decorators/global = array( 'decorator1' )

This would add the decorator named "decorator1" defined by "\Aimeos\Admin\JQAdm\Common\Decorator\Decorator1" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/text/decorators/excludes
  • admin/jqadm/product/text/decorators/local

decorators/local#

Adds a list of local decorators only to the product JQAdm client

admin/jqadm/product/text/decorators/local = Array
(
)
  • Default: Array
  • Type: array - List of decorator names
  • Since: 2017.07

Decorators extend the functionality of a class by adding new aspects (e.g. log what is currently done), executing the methods of the underlying class only in certain conditions (e.g. only for logged in users) or modify what is returned to the caller.

This option allows you to wrap local decorators ("\Aimeos\Admin\JQAdm\Product\Decorator*") around the JQAdm client.

 admin/jqadm/product/text/decorators/local = array( 'decorator2' )

This would add the decorator named "decorator2" defined by "\Aimeos\Admin\JQAdm\Product\Decorator\Decorator2" only to the JQAdm client.

See also:

  • admin/jqadm/common/decorators/default
  • admin/jqadm/product/text/decorators/excludes
  • admin/jqadm/product/text/decorators/global

name#

Name of the text subpart used by the JQAdm product implementation

admin/jqadm/product/text/name = Standard
  • Default: Standard
  • Type: string - Last part of the JQAdm class name
  • Since: 2016.04

Use "Myname" if your class is named "\Aimeos\Admin\Jqadm\Product\Text\Myname". The name is case-sensitive and you should avoid camel case names like "MyName".

standard/subparts#

List of JQAdm sub-clients rendered within the product text section

admin/jqadm/product/text/standard/subparts = Array
(
)
  • Default: Array
  • Type: array - List of sub-client names
  • Since: 2017.07

The output of the frontend is composed of the code generated by the JQAdm clients. Each JQAdm client can consist of serveral (or none) sub-clients that are responsible for rendering certain sub-parts of the output. The sub-clients can contain JQAdm clients themselves and therefore a hierarchical tree of JQAdm clients is composed. Each JQAdm client creates the output that is placed inside the container of its parent.

At first, always the JQAdm code generated by the parent is printed, then the JQAdm code of its sub-clients. The order of the JQAdm sub-clients determines the order of the output of these sub-clients inside the parent container. If the configured list of clients is

 array( "subclient1", "subclient2" )

you can easily change the order of the output by reordering the subparts:

 admin/jqadm/<clients>/subparts = array( "subclient1", "subclient2" )

You can also remove one or more parts if they shouldn't be rendered:

 admin/jqadm/<clients>/subparts = array( "subclient1" )

As the clients only generates structural JQAdm, the layout defined via CSS should support adding, removing or reordering content by a fluid like design.

template-item#

Relative path to the HTML body template of the text subpart for products.

admin/jqadm/product/text/template-item = product/item-text-standard
  • Default: product/item-text-standard
  • Type: string - Relative path to the template creating the HTML code
  • Since: 2016.04

The template file contains the HTML code and processing instructions to generate the result shown in the body of the frontend. The configuration string is the path to the template file relative to the templates directory (usually in admin/jqadm/templates).

You can overwrite the template file configuration in extensions and provide alternative templates. These alternative templates should be named like the default one but with the string "default" replaced by an unique name. You may use the name of your project for this. If you've implemented an alternative client class as well, "default" should be replaced by the name of the new class.

Comments