Monthly Archive for marzo, 2009

Together with the osCommerce Online Merchant v3.0 Alpha 5 release, we have migrated the development repository from a centralized Subversion server to decentralized Git repositories. This replaces the need to access a central server, and requiring the permissions to do so, to allowing you to instantly clone or fork the official development repository to your local development machine. This gives you the complete history of the repository on your local machine where you can start committing your changes to and to share them with others.

The official Git development repository is hosted on Github where developers can network with each other and share the changes they have made.

A screencast presentation is available to show you how easy it is to fork the official repository to make your changes to, and how these changes can be merged back to the official repository.

This is our first screencast presentation and look forward to your feedback. Have fun!

osCommerce Online Merchant v3.0 Alpha 5 introduces a strict level of error reporting directly in the core framework. This is performed by setting the PHP error reporting setting to E_ALL and by setting the MySQL sql_mode to STRICT_ALL_TABLES at runtime.

All warnings and errors are logged in a text file located in the “work” directory and can be easily viewed in the Administration Tool -> Tools -> Error Log application and summary module.

This is the only Administration Tool application where it’s a good sign when it doesn’t show anything. It gives a nice feeling knowing that any sort of warning or error in the core framework has been checked for, from uninitialized PHP variables to problems with MySQL queries.

Setting the error reporting at such strict levels ensures a high quality of coding standards is kept in the core framework and passes this along to add-ons that are developed and installed.

This makes it easier for developers working on addons where they can see where warnings and errors are occuring in what they have been working on, and motivates them to fix the problems to improve the quality of the finalized work.

A configuration parameter will be introduced in v3.0 Beta 1 to disable the output of PHP warnings and errors on the catalog frontend. This allows the output of warnings and errors to occur under development environments, and to be disabled on production servers.