Nice article one, about creating admin modules.

Thanks,
Arya

I try a solution with two applications like descibed in symphony docu http://www.symfony-project.org/book/1_2/02-Exploring-Symfony-s-Code#chapter_02_code_organization

I think it is cleaner solution, at the end you have three diretories frontend backend modules and model directory for the library

greets
aruss

Combined with apache ENV var and different subdomain for each module, it was great.

I try to adapt it with ZF 1.9 but it’s a big mess.

Did you run this structure ?

I use the last structure,
You just have to add this to your bootstrap.php

	$frontController = Zend_Controller_Front::getInstance(); 
	$frontController->throwExceptions(false); 
	$frontController->setControllerDirectory(array('default'=>APP_DIR.'public'.DIRECTORY_SEPARATOR.'controllers','admin'=>APP_DIR.'admin'.DIRECTORY_SEPARATOR.'controllers'));

Also, If you would like to add new modules, change the array passed to the setControllerDirectory (get creative, use a db or ini file etc.., make the admin module do that magic)

I Hope it helps.

yes, module is part of application, eg. works only within it, not alone. But my idea is to develop application, which can accept new modules without changing other code – config files, language files, etc.

I’ve seen proposed structure, but I din’t understood how they are going to deal with admin/public parts. Sure, you can add AdminController.php or have AdminIndex_Action() in controllers, but is this really a good way?

My biggest headache is admin/public distinction. How you do it?

I’m racking my brain on this right now, too and I’m looking at it with regards to the new proposed project structure:

Zend Framework Project Structure

What I think I might have is:

application/
models/
modules/

controller/
models/
view/
[...]

As I see it, the “public” and “admin” section will be sharing the same models, such as a “user” or “account” model. There should be a application level “models” folder for shared resources across modules.

Also, recall that a module *must* be within a context of an application. Sure, it can be a sort of stand-a-lone application, but it’s still part or “plugged-in” to the main application, meaning it should and can be safe to assume certain application level modules will be present to be allowed to be shared.

That’s what I’m thinking at least. That might give you some ideas.

Every quickstart I got for Zend didnt work.

If you have any good links or resources to any Zend related projects I would love to see them.

coolcourt@gmail.com