Hi,
You need the full namespace :
Also, you should be putting this before the 'Doctrine' line in
registerNamespaces()
$loader-registerNamespaces(array(
...
'DoctrineExtensions\\NestedSet' = $vendorDir.'/
doctrine2-nestedset/lib'
));
On 5 jan, 18:33, Yohan 'rouKs' G.
Le 06/01/11 13:58, mwsaz a écrit :
Hi,
You need the full namespace :
Also, you should be putting this before the 'Doctrine' line in
registerNamespaces()
$loader-registerNamespaces(array(
...
'DoctrineExtensions\\NestedSet' = $vendorDir.'/
doctrine2-nestedset/lib'
Kiril, I made sure that filenames and classnames have the same case.
The problem is that the file is autoloaded only in index actions - and
the same file is not autoloaded in any others.
On 14 нояб, 22:21, Kiril Angov [EMAIL PROTECTED] wrote:
Make sure you are using the right name for your file
Having used symfony a lot, I know for a fact that that is not
possible, that is to have autoloading work only in one action and not
in the other. After you change your file names and class names, make
sure you do php symfony cc and then try again.
2008/11/18 [EMAIL PROTECTED] [EMAIL PROTECTED]:
Thanks a lot, Kiril - I just didn't clear cache after I changed the
case, as you told.
On 18 нояб, 15:06, Kiril Angov [EMAIL PROTECTED] wrote:
Having used symfony a lot, I know for a fact that that is not
possible, that is to have autoloading work only in one action and not
in the other.
Make sure you are using the right name for your file myClass.class.php
and MyClass.class.php are different on a case sensitive sistem and I
think that is your problem. PHP classes and functions are not case
sensitive (as far as I know) and if one time you call your class
$something = new
Is it full path to this class?
2008/11/12 [EMAIL PROTECTED] [EMAIL PROTECTED]
Hi folks,
I have noticed the following autoload problem.
I specified a class called MyTools in \lib\myTools.class.php - so it
should be autoloaded anywhere in my application. But it's autoloaded
only in actions
This path is relative to the site root.
I use symfony 1.1 by the way.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
symfony users group.
To post to this group, send email to symfony-users@googlegroups.com
To
Hi,
It seems it should work fine because in SfNestedSetBuilder and
SfNestedSetPeerBuilder classes, the call to addIncludes() method depends
on the addInclude properties so the require() line should not be generated.
http://trac.symfony-project.org/ticket/3716
Can you check your propel.ini use
W odpowiedzi na e-mail od: ruFog otrzymany dnia 2008-09-06 01:07 :
It`s simple to comment require line in Your Base*NestedSet*.php
files ;)
hmm but you must do it every model rebuild
really annoying
--~--~-~--~~~---~--~~
You received this message because
It`s simple to comment require line in Your Base*NestedSet*.php
files ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
symfony users group.
To post to this group, send email to symfony-users@googlegroups.com
To
Hm, I recall having an issue similar to this when I used nested sets
in symfony 1.1 with Propel 1.3. But, uh, I thought that was fixed.
I had to hack together a patch for it, though, but it was ugly as
hell. If you want, I can try to dig it up.
I'm sure it's fixed now though. Hr..!
On Sep
Yohan 'rouKs' G. wrote:
Hi,
I'm migrating from propel 1.2 to 1.3 (symfony1.1) and i've got some
problems with the autoloading...
Fatal error: require() [function.require]: Failed opening required
'lib/model/om/BaseMenuNodePeer.php' (include_path='.:/usr/share/php:/
13 matches
Mail list logo
