Read more this tutorial at the Learning blog.

This would be helpful for debugging your application during development stage.

Simply remove line 18 in index.php if you wish to view errors in the normal PHP way.

Dark version 1440x900

White version 1440x900 | 1920x1080

The new logo resembles a piranha in feeding frenzy (meaning Blazing Fast! for DooPHP). The new look is designed by Valera from Russia, you can view more of his awesome logo designs at BrandBerry.ru.

For instance, you might want to extend the DooValidator. You can write your own validator class in protected/class

Doo::loadHelper('DooValidator');

classs MyValidator extends DooValidator{
     //..??your extended code..
}

And then you can use your extended class in controller:

Doo::loadClass('MyValidator');

Read more tips & tricks at the forum

It shows you how to create a blog with DooPHP. Frontend cache, table relationship, CRUD with the ORM, template engine, data validation and pagination are involved in this blog demo.

The blog demo is included in the download package. Go ahead and try out the blog demo

2 new pages are added to explain the usage of Models and View in DooPHP. It is still recommended that you have a look at the demos since they show you a more complete usage of the features in the framework.

Read more at http://doophp.com/doc/guide/basic/controller

Stay tuned for more advanced guide and demos!

The benchmark comparison of using the original Doo::db() and the new DooModel.

Noticeable New Features in v1.2:

• Enhanced Database ORM for shorter and more elegant code. Your current model classes can extend DooModel for addon ORM functionailities.
• Smart Model Cache (DooSmartModel) for automated data model cache management. It is a smarter version of DooModel. Cache can be stored as file based, php vars, APC, XCache, Memcache, EAccelerator.
• Form/Model Validation for data validation before saving/creating/deleting DB records. Validation rules can be generated with the Model generator.
• Better Native PHP template support for those who do not use the template engine. Read the API doc for DooView.
• And several bug fixes plus enhancements.

View the complete features and changes in the CHANGELOG file in the latest source.

Go ahead and download the new framework source.

See DooPHP database demo's MainController::test() and the API doc for DooModel for example usage of the enhanced ORM tools.

The benchmark comparison of v1.0 and v1.1

The benchmarked source code and environment is the same as the previous benchmark tested with Kohana framework.

Noticeable New Features in v1.1:

• Access Control List(ACL) as built-in authentication support.
• Data caching which supports APC, Memcache, XCache, EAccelerator & file based cache.
• Sophisticated Frontend cache mechanism where both full page(single/recurvise) & partial page cache are supported.
• Database replication (master-slave) support in the ORM tools
• Better conventional modular directory structure support.
• Auto loading of the framework classes.
• IF statement and Cache tag support for template engine.
• Enhanced model class generator. PostgreSQL supported.
• Image manipulation helper for resize, crop, watermark, upload, etc.
• Pager component for item list pagination.
• Text helper class for string manipulation.
• Url builder class to generates URLs based on route ID or controller & method names
• Log/Profile viewer tool.
• Sitemap Generator tool to generate routes and controller files.

View the complete features and changes in the CHANGELOG file in the latest source.

Go ahead and download the new framework source. New demos and tools are added in to help you get started even easier now.

Most simple frameworks/application have no separation of Reads and Writes of the DB. Once the projects outgrow a single server RDBMS the next step is often to do a Master/Slave setup in MySQL.

In a Master/Slave setup expensive and less frequent writes are channeled to the Master server while reads are channelled to the Slave server.

In DooPHP, we simplifies thing to merely just define the Slave server configurations in db.conf.php

You need to call Doo::useDbReplicate() in the bootstrap index.php, and that's all!

The query stuffs remain the same.

To setup:

//This will serve as the Master
$dbconfig['dev'] = array('localhost', 'db', 'root', '1234', 'mysql',true);

//slave with the same info as master
$dbconfig['slave'] = array('192.168.1.1', '192.168.1.2', '192.168.1.3');

//OR ...
//slave with different info, use a string if it's same as the master info.
$dbconfig['slave'] = 
	array(
	   array('192.168.1.1', 'db', 'dairy', '668dj0', 'mysql',true),
	   array('192.168.1.2', 'db', 'yuhus', 'gu34k2', 'mysql',true),
	   array('192.168.1.3', 'db', 'lily', '84ju2a', 'mysql',true),
	   '192.168.1.4'
    );

In index.php just add a line Doo::useDbReplicate() before setting up the DB.

Doo::useDbReplicate();
Doo::db()->setMap($dbmap);
Doo::db()->setDb($dbconfig, $config['APP_MODE']);