>From docs: "When you create a new class: Adding a class to an autoloading directory (one of the project's lib/ folders) is not enough to have symfony find it automatically in non-development environments. You must clear the autoloading configuration cache so that symfony browses again all the directories of the autoload.yml file and references the location of autoloadable classes--including the new ones."
As i understand it, symfony does not recognize new classes until the "config_autoload.yml.php" file is created (on first hit). Clear the cache and call your site in dev mode, and see how much it takes to build that file. I wouldn't like to wait that long on "every" request. Or did i missunderstood you? Michael On Sep 30, 6:27 pm, Carl Vondrick <[EMAIL PROTECTED]> wrote: > On Tue, 2008-09-30 at 00:30 -0700, [EMAIL PROTECTED] wrote: > > If this is true, then i'm not up to date :o( > > I thought this process is running, when there is no > > "config_autoload.yml.php" in the cache ... > > I don't understand the problem with it? If you haven't added any > classes, there is _no_ performance hit. > > Carl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
