Would be great to put this additional info as well to the wiki about new Module Handling if necessary to understand how it works now with 4.6?
-> http://wiki.oxidforge.org/Features/Extension_metadata_file -> http://wiki.oxidforge.org/Tutorials#How_to_Extend_OXID_eShop_With_Modules_.28Part_1.29 -> http://wiki.oxidforge.org/Tutorials#Create_a_backend_module_-_1._Getting_started Of course I can help adding new info to the wiki, no matter what language - but as I am not a coder, I would need a whitepaper first. Ray ________________________________________________ Haller Stahlwaren GmbH Am Gartennest 1 74544 Michelbach/Bilz --- Tel.: 0791/47003 Fax : 0791/47005 www.haller-stahlwaren.de --- Sitz: Schwäbisch Hall Registergericht: Stuttgart HRB 570131 Geschäftsführer: Hermann Hebsacker, Karin Hebsacker -----Ursprüngliche Nachricht----- Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von WBL Björn Lange Gesendet: Montag, 14. Mai 2012 23:28 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] new module structure in 4.6 and admin include files not working? Good Evening Stefan, Am 14.05.2012 22:00, schrieb Stefan Moises: > Hello Björn, > > thanks a lot, good idea to use functions.php and oxutilsView to load the > admin includes even in oxajax.php and the overwritten templates from the > module directory! > Now I have everything loaded and packed nice and clean in my module dir, > no need to copy anything into the core shop dirs anymore... sweet :) Yeah, sure. No Problem! > > If anybody else is using "admin/inc/...inc.php" file includes in custom > modules, just add this to your functions.php file: > > # add module admin dirs to include path to get the "admin/inc/*.inc.php" > files working! > $aModuleDirs = glob( dirname(__FILE__) . '/*/admin/', GLOB_ONLYDIR); > $aModuleDirsVendor = glob( dirname(__FILE__) . '/*/*/admin/', > GLOB_ONLYDIR); > $aIncludeDirs = array_merge( $aModuleDirs, $aModuleDirsVendor ); > if (is_array($aIncludeDirs) && count($aIncludeDirs)) { > foreach($aIncludeDirs as $sIncDir) { > set_include_path(get_include_path() . PATH_SEPARATOR . $sIncDir); > } > } I would not do it like this, i think this is way to much overhead. > > I guess I will write a little blog entry this week about all the little > pitfalls when updating modules to Oxid 4.6... Yeah that would be nice, maybe this <http://ecommerce-developer.de/unser-oxid-autoloader/> <http://ecommerce-developer.de/wbl-autoloader-und-oxid-4-6-0/> Can help you too. Still working on the translation and the oxid project. @Marco Steinhäuser Is there still the possibilty to get the github project rep for the autoloader, even when the translation is not done yet? Regards, Björn -- ___________________________________ WBL Konzept, Beerden &Lange GbR Björn Lange Geschäftsführender Gesellschafter Luxemburger Straße 266 50937 Köln Telefon: 0221 282 755 82 www.wbl-konzept.de www.facebook.com/wbl.konzept b.la...@wbl-konzept.de _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
