[symfony-users] Problems with no_script_name=off after upgrading from Symfony 1.2.8 to 1.3.1

Hello I have a Symfony 1.2 project that I tried to convert to Symfony 1.3. The no_script_name setting is turned off (verified with the debug console) yet in Symfony 1.3 it behaves like it was turned on! The same link_to('Störungsursachen', 'gu_ursache') produces https://example.com/proxy/fibr

Re: [symfony-users] Problems with no_script_name=off after upgrading from Symfony 1.2.8 to 1.3.1

Change 'on' to 'true' http://www.symfony-project.org/tutorial/1_4/en/upgrade#chapter_161aacbf11b8cc24bbdc6951ba0fb57d_yaml On Wed, Jan 6, 2010 at 11:41, Christian Hammers wrote: > Hello > > I have a Symfony 1.2 project that I tried to convert to Symfony 1.3. > The no_script_name setting is turned

Re: [symfony-users] Problems with no_script_name=off after upgrading from Symfony 1.2.8 to 1.3.1

Hi Thanks for the quick reply, you saved my day! Too bad that symfony does not give a warning if a boolean value is set to something different than "true" or "false". bye, -christian- On Wed, 6 Jan 2010 12:07:25 +0100 Gábor Fási wrote: > Change 'on' to 'true' > http://www.symfony-project.org