Comments on: GSoC, ZF & Doctrine

By: Abhishek Kushwaha

Abhishek Kushwaha — Mon, 07 Jun 2010 13:53:30 +0000

Yes Ruben,
please make it as soon as possible…..
I am eagerly waiting for the assistance in integrating ZF 1.10 and Doctrine 1.2.2
:)

By: RubenV

RubenV — Sun, 08 Nov 2009 12:26:12 +0000

Master thesis has been finished for quite some time now. Right now it’s the PhD that’s keeping me from updating this to ZF 1.10.

By: Dieter

Dieter — Sun, 08 Nov 2009 08:18:58 +0000

Great tutorial, it really helped me out in my setup.
More of these after the Master thesis? ;-)

By: Lisa Ridley

Lisa Ridley — Mon, 21 Sep 2009 21:42:06 +0000

Hey! Love your tutorial; however I was getting a PHP Notice when trying to use Doctrine 1.1.3 and Zend Framework 1.8.2 together:

Notice: Zend_Loader::Zend_Loader::registerAutoload is deprecated as of 1.8.0 and will be removed with 2.0.0; use Zend_Loader_Autoloader instead in [...]/library/zendframework/Zend/Loader.php on line 207

which stack-traces back to the following line in /application/global.php:

Zend_Loader::registerAutoload(‘Zend_Loader’);

After doing some research it appears that this notice was introduced as of Zend Framework version 1.8 due to the deprecation and future removal of the autoloader feature of Zend_Loader. The fix I found is as follows:

Replace the following lines in /application/global.php:

require_once(‘Zend/Loader.php’);
Zend_Loader::registerAutoload(‘Zend_Loader’);

with these:

require_once(‘Zend/Loader/Autoloader.php’);
$autoloader = Zend_Loader_Autoloader::getInstance();
$autoloader->setFallbackAutoloader(true);

and your tutorial will run properly, although I don’t have a full understanding of the implications of the change since I”m not really clear on why the autoload mechanism in Zend_Loader is being deprecated to begin with, although I think it’s related to the introduction of Namespaces in php 5.3.0, and future enhancements to support them properly in the Zend Framework.

A second issue that arose is the following notice when error reporting is set to include E_STRICT:

Strict standards: Only variables should be passed by reference in [...]/library/doctrine/Doctrine/Query.php on line 1187

which appears to be triggered by a call to Doctrine_Query::execute(), as occurs in IndexController::indexAction() on the following lines:

$message_query = Doctrine_Query::create()
->select()
->from(‘Message m’)
->orderBy(‘m.posted DESC’);
$messages = $message_query->execute();

Again, not alot of information, although this appears to be triggered by Doctrine itself.

Great tutorial, by the way.

By: Yuta

Yuta — Tue, 09 Jun 2009 13:39:31 +0000

Hi Ruben,

I translated your nice tutorial into Japanese and published it.
http://studiokdf.com/blog/2009/06/66.html

Thanks.

By: RubenV

RubenV — Sat, 06 Jun 2009 22:10:03 +0000

@danceric: Cool! Thanks, that’ll help to keep people going!

By: danceric

danceric — Sat, 06 Jun 2009 12:14:49 +0000

Hi Ruben, I have updated the instruction here for ZF 1.8 at http://www.danceric.net/2009/06/06/doctrine-orm-and-zend-framework/
feel free to take anything you want if you want to update your great post.

By: RubenV

RubenV — Sat, 30 May 2009 17:01:01 +0000

I need to update the article for ZF 1.8, but that won’t be for any time soon, as I’m bogged down by my masters thesis.

By: will

will — Thu, 28 May 2009 08:05:52 +0000

Hay, out of interest. you can’t really have zend_db models anymore right? wouldn’t it be better to have the doctrine models in their own folder? maybe inside the models folder?

By: will

will — Thu, 28 May 2009 04:59:44 +0000

ok, self rescue: I put this in my bootstrap class, zf seems to call it for me

protected function _initDatabase()
{
Doctrine_Manager::connection(“mysql://root:root@localhost/track”);

Zend_Registry::set(‘doctrine_config’, array(
‘data_fixtures_path’ => dirname(__FILE__).’/doctrine/data/fixtures’,
‘models_path’ => dirname(__FILE__).’/models’,
‘migrations_path’ => dirname(__FILE__).’/doctrine/migrations’,
‘sql_path’ => dirname(__FILE__).’/doctrine/data/sql’,
‘yaml_schema_path’ => dirname(__FILE__).’/doctrine/schema’
));
}

Then in index.php, i added the generated models path, cos the models file structure / class names don’t match ZF’s autoloading pattern (?)

// Ensure library/ is on include_path
set_include_path(implode(PATH_SEPARATOR, array(
realpath(APPLICATION_PATH . ‘/../library’),
realpath(APPLICATION_PATH . ‘/models/generated’),
get_include_path(),
)));

oh, its not just generated, so just for a little variation, i added to the incude path in the config by sticking this line in the ini

includePaths.model = APPLICATION_PATH “/models”

presumable ZF adds any includePaths.whatevers to the path, why not say that in the comments is a bit of a mystery to me, i guess they only want *really clever* developers using it. grumble grumble.