Re: [oxid-dev-general] Translations for module settings? How?

2013-02-06 Thread André Herrmann
Hi Nicolas, Hi Gernot, does this also work for frontend themes? I mean, in most cases the theme folder is customized so the module cannot rely on having azure for example. Or does the subfolder place not harm the basic functionality of module_options.php? @oxid: Please document the translation

Re: [oxid-dev-general] Translations for module settings? How?

2013-02-06 Thread Nicolas Hodin
Hi André, I don't think so. The module_options.php file is located in out/admin/en/ in the module directory, so I think it's used only for the Settings tab in the Admin theme. If you need to add translations for your module (and be sure that it will be available on front theme), you have to

[oxid-dev-general] Template Changes in Minor Versions

2013-02-06 Thread Frank Zunderer
Hi all, while answering a forum post i stumbled across this bug: https://bugs.oxid-esales.com/view.php?id=4240 This is not resolved in current version because: as this does require template changes, we will release it only in 5.1. For earlier versions please use this fix ... I understand the

Re: [oxid-dev-general] Template Changes in Minor Versions

2013-02-06 Thread Dainius Bigelis
Hi, Very interesting topic, btw. And I would like to hear more opinions about that, especially from those, which do support for several (or much more) shops and need to keep that up-to-date (means invest lot of time and money for updating to latest version). So - do you prefer to invest more