HI!

I would say not to modify the file. I had this problem and i have fix it in
this method:

Assuming that you have access to the parent directory (let's say is a whm /
cpanel powered host)

So, my parent directory looks like :

- access-logs
- etc
- mail
- public_ftp
- public_html
- sf_project
- tmp
- www
- [some .hidden files ]

I guess it is obvious what i do have in the sf_project directory, but i will
digg into it and i will show you something else:

in the file: /sf_project/config/ProjectConfiguration.class.php

i have this piece of code:

<?php

# FROZEN_SF_LIB_DIR: /srv/symfony/1.2/lib

require_once
dirname(__FILE__).'/../lib/symfony/autoload/sfCoreAutoload.class.php';
sfCoreAutoload::register();

class ProjectConfiguration extends sfProjectConfiguration
{
  public function setup()
  {
    // for compatibility / remove and enable only the plugins you want
    $this->enableAllPluginsExcept(array('sfDoctrinePlugin',
'sfCompat10Plugin'));
*    $this->setWebDir('/home/alecslup/public_html/');*
  }
}

So, we go now upper, in the public_html folder where we have:

- cgi-bin
- css
- images
- js
- sf
- sfAdminDashPlugin
- sfFormExtraPlugin
- sfJqueryLibsPlugin
- sfPropelPlugin
- sfProtoculousPlugin
- sfSimpleBlogPlugin
- symfony
- uploads
- index.php
- backend.php
- some other files

So, we now open the index.php file, and we can see the code:

<?php

require_once(dirname(__FILE__).'/..*/sf_project/*
config/ProjectConfiguration.class.php');

$configuration =
ProjectConfiguration::getApplicationConfiguration('frontend', 'prod',
false);
sfContext::createInstance($configuration)->dispatch();

As index.php is in public_html and symfony project is located into
../sf_project/ I have changed the require_once file path and now all the
stuff is working smoothly.

You can test the application at the url:

http://www.alecslupu.ro/

Alternativelly, you can test the frontend here, but it is closed as this is
the default in a sf Project.

http://alecslupu.ro/frontend_dev.php/

I hope my email has helped you. If you still have problems, let me know.

Alecs

On Fri, Nov 27, 2009 at 9:38 AM, dziobacz <[email protected]> wrote:

> Here is my message about problems when all symfony files are in
> public_html (root directory) and ALSO my solution (or rather solution
> which I have found on polish site) - it is important - so could
> somebody do that in new version of symfony ??
> http://trac.symfony-project.org/ticket/7543
>
> Thx this solution ALL symfony files can be placed in catalog
> public_html OR normal: Symfony files from /web Symfony catalog in
> catalog /public_html on the server and all other symfony files above
> catalog /public_html on the server - it doesn't matter - it will be
> always ok :) This is very important.
>
> --
>
> 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]<symfony-devs%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en.
>
>
>


-- 
Have a nice day!
Alecs

As programmers create bigger & better idiot proof programs, so the universe
creates bigger & better idiots!
I am on web:  http://www.alecslupu.ro/
I am on twitter: http://twitter.com/alecslupu
I am on linkedIn: http://www.linkedin.com/in/alecslupu
Tel: (+4)0748.543.798

--

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.


Reply via email to