Okay here's a solution that should work for ya...
in your app.yml do something like this:
all:
sf_guard_plugin:
success_signout_url: module/action
That should do it for ya. I have tried it out and have no problems
with the trailing slash. Also make sure you don't have some kind of
rewrite rule going on that may be causing that trailing slash.
Regards
- Keith
On Oct 23, 1:25 am, Ant Cunningham <[EMAIL PROTECTED]>
wrote:
> Actually no. I hadnt tried that. Ill try changing it to the default module
> instead of just / tomorrow. Still though id like to know if this is an issue
> with my hosting set up or if this is just what it does... Of course I have a
> feeling all this will become a non-issue in 1.1.
>
> On 10/23/07 12:22 AM, "me" <[EMAIL PROTECTED]> wrote:
>
>
>
> > You may have already played with this, but have you changed your
> > @homepage route? I know that sfGuard will automatically redirect to
> > your @homepage whenever it successfully logs in to the system.
>
> > On Oct 19, 12:35 pm, Ant Cunningham <[EMAIL PROTECTED]>
> > wrote:
> >> Well my issue isnt with assets... those all work properly. My issue is with
> >> the pages themselves... for example:
>
> >>www.domain.com/backend_prod.php
>
> >> gets redirected to
>
> >>www.domain.com/backend_prod.php/
>
> >> which results in the message "No input file specified."
>
> >> Note: this was only happening on IE initially. Now after I tried tinkering
> >> a bit to fix it its happening in IE and Mozilla/KHTML (stupid me trying to
> >> tinker).
>
> >> On 10/19/07 12:00 PM, "Jay Klehr" <[EMAIL PROTECTED]> wrote:
>
> >>> Shouldn't you either use absolute URLs for your assets, or use an
> >>> initial trailing slash?
>
> >>> Symfony's URL structure makes use of "pretty urls" for parameters, so
> >>> it's not uncommon to see "site.com/users/list/page/2"
>
> >>> Trailing slash or not your CSS and Images won't load if you're not
> >>> accessing them like "/css/main.css" with paths like the above.
>
> >>> I'd suggest making your CSS and other assets work with or without the
> >>> trailing slash, as I think you'll always see that issue come up with
> >>> Symfony.
>
> >>> Jay
>
> >>> Jonathan Franks wrote:
> >>>> sfGuard is working perfectly for me except for one problem. After log
> >>>> in, it adds a trailing slash to the url...
>
> >>>>www.mysite.com/backend.php
>
> >>>> becomes
>
> >>>>www.mysite.com/backend.php/
>
> >>>> This stops the css from loading (and probably any other assets)
>
> >>>> Am I doing something wrong? // Regards Jonathan
--~--~---------~--~----~------------~-------~--~----~
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 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
-~----------~----~----~----~------~----~------~--~---
