Eligijus Vitkauskas
Eligijus Vitkauskas
@alfredbez Totally agree on refactoring application to use Symfony console component, now especially when oxid has composer support this makes sense more than ever. As keywan already mentioned I've started...
1.3 oxid-console installation will be through composer only, so you can install globally and run oxid console commands in a directory where shop source lies, or in a project itself...
In order to have oxid console executable in oxid project directory itself (non vendor directory) we would have to make people to put it there manually (as we do it...
Hello @keywan-ghadami-oxid, Can you please explain me what do you mean by unable to fix new modules on subshops? Or yet better, give me your use case. Currently `_getAvailableModuleIds()` should...
@keywan-ghadami-oxid Alright. I'll test it and evaluate the problem on a weekend. Stay patient! (:
Can not really test it against EE version as I do not have access to it but I take your word that there is a bug on this. One little...
@keywan-ghadami-oxid I am aware of that calling `_getModulesFromDir()` on every shop oxConfig is the part of the fix. But within this pull-request you are also doing `_parseModuleIds()` on every shop...
Thanks for a good suggestion! +1