Re: [oxid-dev-general] Write debug-output to files instead to browser?

Hi Roman, use oxUtils::getInstance()->writeToLog( $sLogMessage, $sLogFileName ); things will land in log folder then. Best wishes André Am Mittwoch, 28. August 2013, 15:19:37 schrieb Roman Allenstein: > Is there a way not to print the debug-output to the browser but log it > instead in to fi

Re: [oxid-dev-general] Coding Guidelines

Hi Roman and welcome to this list. > Does OXID provide any coding-guidelines for developing own modules? Yep. Have a look at this tutorials: http://wiki.oxidforge.org/Tutorials#Modules_and_Extensions Additionally, it's probably worth to invest in this book: http://oxid-kochbuch.de/ Good luck! M

[oxid-dev-general] Write debug-output to files instead to browser?

Is there a way not to print the debug-output to the browser but log it instead in to files? Greets Roman Allenstein -- Dipl.Winf. (FH) Roman Allenstein Software-Developer Spark 5 GmbH Rheinstraße 97 64295 Darmstadt Fon: +49-6151-8508-048 Fax: +49-6151-8508-111 Mail: roman.allenst...@spark5.de

[oxid-dev-general] Coding Guidelines

Does OXID provide any coding-guidelines for developing own modules? Greets Roman Allenstein -- Dipl.Winf. (FH) Roman Allenstein Software-Developer Spark 5 GmbH Rheinstraße 97 64295 Darmstadt Fon: +49-6151-8508-048 Fax: +49-6151-8508-111 Mail: roman.allenst...@spark5.de Web: http://www.spark5.de

[oxid-dev-general] OXID eShop versions 5.0.7 and 4.7.7 published

HI everybody, OXID eShop versions 5.0.7 (EE) and 4.7.7 (PE, CE) were published containing bug fixes and some slight changes in admin templates and language files. As always, you'll find all relevant information on this wiki page: http://wiki.oxidforge.org/Downloads/4.7.7_5.0.7 Best! Marco _