Gang,
I'm having the same issue, any thoughts into how it is corrected?
It should just work right? It has to be something extremely simple we're
missing right?
-B
joedevon wrote:
spaceage wrote:
I can appreciate what you are saying re: Zend_Form, but it shouldn't be
an issue whether
Here's the default autoloader as output from xdebug...note that is using a
namespace of 'My_' in the Zend_Application_Module_Autoloader object (so not
exactly default). Hopefully a cleaned up explanation of this will make it
into the online manual soon:
I have a new project set up via Zend_Tool...the directory structure is
totally standard:
/application
bootstrap.php
/configs
/controllers
/layouts
/models
/views
/library
/public
index.php
My include_path is set entirely in index.php:
Vlad--thanks for this tip...I believe this is the same advice from the
quickstart. I tried this with the namespace set to '' (so I don't have to
prefix class names with Default_) without success.
Having said this, how does the autoloader get initialized for the Zend
library in my installation?
I set up my Bootstrap without a namespace either and added this to
application.ini to get my modules to show:
resources.frontController.moduleDirectory = APPLICATION_PATH /modules
--
View this message in context:
So did you just put the path(s) to the dirs you want autoloading for in
application.ini?
I tried this, ie:
includePaths.library = APPLICATION_PATH /../library
includePaths.models = APPLICATION_PATH /models
which does result in my include_path getting set appropriately, but
autloading is still
What's yr error message?
I assume you have a dir structure like:
/application
/application/modules
/application/modules/mymodule
/application/modules/mymodule/controllers
./models
/views
etc?
--
View this message in context:
spaceage wrote:
Its the default structure as setup by Zend_Tool:
/application
bootstrap.php
/configs
/controllers
/layouts
/models
/views
/library
/public
index.php
You don't have a modules directory under application. And I get the feeling
you don't
Joe--thanks for your input.
My include path is (1) the library dir where ZF is located, (2) the
/application/models dir and (3) .
I'm a little unclear when you say once it knows path to application it will
figure out path to models: wouldn't this also be the case if instead of
using
spaceage wrote:
My include path is (1) the library dir where ZF is located, (2) the
/application/models dir and (3) .
You don't need /application/models in the path. Remove the line that sets
it. It's just adding an extra path to slow down the system a bit.
I'm a little unclear when
OK, this makes sense, but its still failing...
In index.php, I have:
defined('APPLICATION_PATH')
|| define('APPLICATION_PATH', realpath(dirname(__FILE__) .
'/../application'));
and
set_include_path(implode(PATH_SEPARATOR, array(
realpath(APPLICATION_PATH . '/../library'),
spaceage wrote:
class Model_LoginForm extends Zend_Form
Oops, yeah you're using Zend_Form. that goes here:
/application/forms
and the file should be named Login.php and begins
class Form_Login extends Zend_Form
I haven't used Zend_Form yet, been doing forms manually but will try it
asideLest you get the wrong idea--I love ZF. It rocks. I could make some
suggestions re: docs, but what is available is pretty good already./aside
I can appreciate what you are saying re: Zend_Form, but it shouldn't be an
issue whether the class def is in application/models vs.
spaceage wrote:
I should add that 'model' and 'models' were being used interchangeably in
both of our posts, and I've updated everything to be 'models'/'Models'
throughout...
I don't know how I missed this post...I wasn't using model and models
interchangeably...You need to remove plural
Joe--I have to study this more closely, but from the table you have provided,
it would appear that certain assumptions are being made by the autoloader
I'm not aware of...too bad this table isn't in the docs ;-) Thanks--I will
study your suggestions and see if I can end my 2 day loss of time.
15 matches
Mail list logo
