I've been having the same issues at my site.  Users have used names
like john.doe or [email protected] and this does not work.  I followed the
instructions in this link:

http://bluehorn.co.nz/2008/12/04/how-to-handle-dot-in-symfony-url/

But I still encounter the 404 error.  I've been having to go back into
customer's accounts and change their usernames.

Out of curiosity has anyone come up with a username validator?  For
example, I could see if the username had a "/" in it, that would cause
further issues even if we resolve the "." issue.  Ideally the username
validator would extend the Regex validator and define a set of rules.

Of course I already have a number of usernames that do things like
include the # symbol in their username.

Regards,
Steve


On Oct 19, 4:57 pm, Alexandre SALOME <[email protected]>
wrote:
> And what about logs ?
>
> Do they talk of your route ?
>
> Does it works with an URL with some text instead of mail ?
>
> /unsubscribe/email/test for example.
>
> Alexandre
>
> 2009/10/19 Eno <[email protected]>
>
>
>
>
>
> > On Mon, 19 Oct 2009, Alexandre SALOME wrote:
>
> > > Does it enter the action ?
>
> > Doesn't get that far, because the module and action name don't appear to
> > get matched at all.
>
> > > What does log files tell ? Which route did it matches ?
>
> > > What kind of error do you have in development environment ? Stack trace ?
>
> > Yeah, sfError404Exception:
>
> > 404 | Not Found | sfError404Exception
> > Empty module and/or action after parsing the URL
> > "/unsubscribe/email/[email protected]" (/).
> > stack trace
>
> >    * at ()
> >      in SF_SYMFONY_LIB_DIR/controller/sfFrontWebController.class.php line
> > 44 ...
> >              41.
> >              42.       if (empty($moduleName) || empty($actionName))
> >              43.       {
> >              44.         throw new sfError404Exception(sprintf('Empty
> > module and/or action after parsing the URL "%s" (%s/%s).',
> > $request->getPathInfo(), $moduleName, $actionName));
> >              45.       }
> >              46.
> >              47.       // make the first request
> >    * at sfFrontWebController->dispatch() in
> > SF_SYMFONY_LIB_DIR/util/sfContext.class.php line 159 ...
> >             156.    */
> >             157.   public function dispatch()
> >             158.   {
> >             159.     $this->getController()->dispatch();
> >             160.   }
> >             161.
> >             162.   /**
> >    * at sfContext->dispatch()
> >      in /home/web/htdocs/index.php line 10 ...
>
> > Which isn't very useful :-)
>
> > --
>
> --
> Alexandre Salomé -- [email protected]
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to