I know this is an old thread, but in case anyone finds it in the
archives, I wanted to report that I resolved the issue by upgrading
php and mysql on the specific server that was giving me trouble.
The currently running versions are:
PHP 5.2.4
mysql Distrib 5.0.45
On Nov 27, 9:59 am, forkmantis <[EMAIL PROTECTED]> wrote:
> Thanks, Ryan.
>
> I have quadruple-checked for the presence of the myUser.class.php
> file, and have cleared cache so many times the paint is flaking off
> of the "c" key on my keyboard.
>
> As you suggested, I built a new frontend controller for the search
> environment and browsed through the site using that controller. Here
> is what I have found:
>
> * the lucene-init task does not generate a config_autoload.yml.php in
> the /cache/admin/search/config directory
> * browsing the site w/ the search environment front controller does
> create config_autoload.yml.php in the /cache/admin/search/config
> directory
> * running the lucene-init task after the config_autoload.yml.php file
> exists still results in the fatal error for not being able to find the
> myUser.class.php file.
> * On a separate server, lucene-init does generate the
> config_autoload.yml.php file and execute without error.
>
> It would seem that the trouble I'm encountering is related to my
> development server, and not to the project itself.
>
> After running the task on another server, I see that it just generates
> two search.yml files. I'll be glad to pitch in and help w/ further
> troubleshooting if anyone else encounters a similar problem.
> Otherwise, I've manually copied the search.yml files over from the
> other server and am content to move on.
>
> Thanks again for your detailed help.
>
> On Nov 27, 7:07 am, weaverryan <[EMAIL PROTECTED]> wrote:
>
> > Sticking my head out here a little as I haven't used this plugin yet,
> > but I would check a few things.
>
> > In essence, the myUser class isn't being found for the specific
> > application. First, be absolutely sure that
> > the myUser.class.php file is located in the /apps/<app>/lib directory.
> > Double, Triple check that this file is
> > present (I have no idea why it wouldn't be there). Also, double,
> > triple check that the cache is cleared.
>
> > This task handles is library autoloading in the file sfLucenePlugin/
> > data/tasks/sfPakeLucene.php file
> > in the _load_application_environment() function. This function
> > initializes the application using the search
> > environment, so you absolutely should have a file called
> > config_autoload.yml.php in your
> > cache/<app>/search/config after running this task. Why you wouldn't
> > have that file is a mystery. Without
> > this file, nothing is being loaded - so it makes sense that myUser
> > wouldn't be found.
>
> > Again, there area 1000 reasons why this might happen - but in 99.99%
> > of the cases, it's something simple
> > like not clearing the cache, or some strange change you've made in
> > your application.
>
> > One thing you might do is create a new frontend controller, maybe
> > search.php in your web folder with the following
> > contents:
>
> > <?php
>
> > define('SF_ROOT_DIR', sfConfig::get('sf_root_dir'));
> > define('SF_APP', $app);
> > define('SF_ENVIRONMENT', 'search');
> > define('SF_DEBUG', true);
>
> > require_once
> > SF_ROOT_DIR.DIRECTORY_SEPARATOR.'apps'.DIRECTORY_SEPARATOR.SF_APP.DIRECTORY_SEPARATOR.'config'.DIRECTORY_SEPARATOR.'config.php';
>
> > sfContext::getInstance()->getController()->dispatch();
>
> > Now, surf to your application/search.php (or whatever you called the
> > above controller). Surfing this application is in essence what the
> > lucene task is trying to do. Any errors here are most likely
> > being suffered by the lucene task as well. By surfing this app, you
> > should absolutely now have a config_autoload.yml.php in the above-
> > mentioned cache directory.
>
> > Hopefully this gives you something to chase after.
>
> > Ryan
>
> > On Nov 26, 4:46 pm,forkmantis<[EMAIL PROTECTED]> wrote:> I checked out the
> > project I am having trouble with onto a new
> > > machine. On the new machine, I was able to execute the lucene-init
> > > task successfully. On the original machine, I deleted the entire
> > > project and did a fresh checkout from svn, and am still not able to
> > > execute the task.
>
> > > I did notice that on the second machine under the cache/<app>/search/
> > > config directory I had a config_autoload.yml.php file, but on the
> > > original machine this file was missing. So it appears for some reason
> > > that the config_autoload.yml file is not being generated on one server
> > > while it is on the other. I don't see anything interesting in the
> > > <app>_search.log file to indicate what the problem may be.
>
> > > On Nov 26, 10:03 am,forkmantis<[EMAIL PROTECTED]> wrote:
>
> > > > Thanks for the response, Carl.
>
> > > > I have just checked out -r6162 of sfLucenePlugin into my project,
> > > > cleared cache, and looked at my factories.yml for the application in
> > > > question. The commented defaults have not been altered:
>
> > > > # user:
> > > > # class: myUser
>
> > > > I still get this error when running "symfony lucene-init <app>":
>
> > > > PHP Fatal error: Class 'myUser' not found in <path>/lib/symfony/user/
> > > > sfUser.class.php on line 107
>
> > > > I'm not totally sure how to troubleshoot from here.
>
> > > > Carl Vondrick wrote:
> > > > > On Friday, November 23, 2007,forkmantiswrote:
> > > > > > PHP Fatal error: �Class 'myUser' not found in
> > > > > > /<path>/lib/symfony/user/
> > > > > > sfUser.class.php on line 107
>
> > > > > Hi,
> > > > > This issue is not related to sfLucene. Try clearing your cache and
> > > > > checking
> > > > > your configuration factories for the user.
>
> > > > > Carl
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
