Home
Welcome to the mude_easy_admin wiki!
The idea is to make extension to the OXID eShop admin much more easy. When building a module one often needs some config (oxconfig) settings. With this module adding a few settings just takes a few seconds.
Another idea is to “outsource” the module configuration (aModules array in oxconfig) in order to make it possible to:
- keep it during developmen in svn
- deploy such settings much easier to a server
- merge multiple settings
- edit the module configuration in case shop is broken
- config.xml are not merged yet (only first config.xml is used)
- multiple select element not supported yet
- code is still in spike solution mode … this means no doc :(
- add key / value array as config setting
- extract modul configuration to external file(s)
- allow extension of article, category etc etc.
- … feel free to add more …
This modules improves the extensibility of the OXID eShop admin.
It introduces a new smarty plugin called mude_easy_admin_config_input. It can be used in every config templates (e.g.shop_config.tpl) with a view class based on shop_config.
It will create a element for user input of an oxconfig value.
Possible calls are:
$sSetting → the id under which the value will be stored in the DB, also 2 Lang constants are needed: CONFIG_$sSetting and HELP_$sSetting
[{mude_easy_admin_config_input name=$sSetting type="checkbox"}] —> checkbox
[{mude_easy_admin_config_input name=$sSetting type=“select” options=$oElement→options}] —> select element with options as array ID → value
[{mude_easy_admin_config_input name=$sSetting type="text"}] —> text field input
[{mude_easy_admin_config_input name=$sSetting type="array"}] —> textarea box for an OXID config array element
All files called “config.xml” in subfolder of “modules” directory will be parsed. Have a look at “example_config.xml” in installation folder.
A new Tab in Master Settings → Core Settings should appear.