I would like to know how to allow a "?" character in a route parameter in Symfony2. This is the route that I have (actually, the route parameter I am focusing on is "messtext"):
ikproj_groupe_sendreply1:
pattern: /{groupid}/{receiver}/{messtext}/{cible}/sendreply
defaults: { _controller: IkprojGroupeBundle:Messages:SendReply1 }
requirements:
messtext: .+
In fact, I had a look at this link: http://symfony.com/doc/current/cookbook/routing/slash_in_parameter.html which is about how to allow a "/" character in a route parameter in Symfony2. I did what I learnt from that tutorial exactly but the problem is that it doesn't work: Symfony2 still displays this error message:
No route found for "GET /groupe/sendreply/11/28/hello,%20dear%20sir...can%20I%20join%20your%20group"
So, my questions are: what is wrong in my code above and how can I resolve that?
Only 1 parameter of your route may accept '/' character. And this MUST be the last one as every following one are considered as part of the param value... In your case, Symfony routing never detect cible and sendreply parts of the URL.
Try to put messtext param at the very end of the URL :
ikproj_groupe_sendreply1:
pattern: /{groupid}/{receiver}/{cible}/sendreply/{messtext}
defaults: { _controller: IkprojGroupeBundle:Messages:SendReply1 }
requirements:
messtext: .+
Related
Thanks to my URL I can know what language and which article the user is looking for instance: article/id_aritlce/Title_of_article/FR
In case the user doesn't write the url with the language information I settle default value in the routing.yml file.
Site_Article:
path: /article/{id}/{article_title}/{language}
defaults: {_controller: SiteBlogBundle:Blog:article, language: EN}
it is working just fine....
but if I type in the URL article/3/Titleofarticle/EN, then EN disapear from the URL. which is not what I want. (I still get the right page, which is with the EN language being display, but still would like to see it in the URL.)
You can not provide default value for en locale and it always be in url when you type it.
But in this case to enable route /article/{id}/{article_title} without any locale you need to create one more route that will not have this parameter at all. In this case Symfony will choose locale based on your fallback_locale parameter that you set in config.yml
Your routing config must look like this:
Site_Article_With_Locale:
path: /article/{id}/{article_title}/{_locale}
defaults: {_controller: SiteBlogBundle:Blog:article}
Site_Article:
path: /article/{id}/{article_title}
defaults: {_controller: SiteBlogBundle:Blog:article}
problem:
need to have urls like this:
wall:
pattern: /{username}/
But.. it match every url like /Messages/, /Settings/
And only solution which comes to mind is to check if this user exists... and if no redirect to the real /Settings ? But its one select for each page and i dont like it.
Is there any other way? + i also probably need to denied register users with routes patterns? How?
AND NO I DONT WANT TO ADD TO URL SOMETHING LIKE /User/{username}
According to my comment, this could be a workaround:
pages:
pattern: /{page}/
requirements:
page: "(Messages|Settings|SomeOtherPage|YetAnotherPage)"
wall:
pattern: /{username}/
Basically, it requires that Page (Settings, Messages, etc) starts with uppercase ([A-Z]) and the rest of page name is not important.
As for the user-profile pages, they should start explicitly with lowercase character ([a-z]).
I don't know if this suffices your requirements...
EDIT:
This is in fact a bit simplified solution of #tomas.pecserke. I have just edited routing so all the pages are enumerated in single route.
I strongly recommend against this approach. You should definetly prefix the route. But if you must do it this way, you can specify other routes first. RouteMatcher chooses the first route that matches the pattern.
# src/Acme/DemoBundle/Resources/routing.yml
account:
pattern: /account
defaults: # ...
some_other_route:
pattern: /some_other_route
defaults: # ...
wall:
pattern: /{username}/
defaults: # ...
# you can set requirements
requirements:
username: [a-z0-9]+ # regular expression
Ich have a problem with symfony2(2.0.16) routing.
I try to run 2 routes like
route1:
host/my/route/{param}
requirements:
param: ".*[^/]$"
route2:
host/my/route/category/{param}
requirements:
param: ".*[^/]$"
As you can imagine, the second route will not be called, not matter what..
what i actually want to do is a search and a specialized search, therefore i need to allow also dots, plus and slashes..
I tried to encode the slash (urlencode to %2F or %252F) so that i can change the requirement, but symfony always decodes it before the routing, so i get an routing error if i remove the requirement.
I thought about to use base64 encoding, but that cant be the solution to my problem..
EDIT: i can also not rely on the order of the routes, because i import the routes from many diffrent bundles..
#This one before the other to be considered !
route2:
host/my/route/category/{param}
requirements:
param: ".+"
route1:
host/my/route/{param}
requirements:
param: ".+"
The parameter for your first route can't be category else it will match it instead of ignoring it. You can change the regex to ignore this value:
route1:
host/my/route/{param}
requirements:
param: "(?!category/).*[^/]$"
route2:
host/my/route/category/{param}
requirements:
param: ".*[^/]$"
Now a parameter called category followed by a slash will be ignored and the pattern won't match, except by the second route.
In the first versions of Sf2 (first Beta's), there was an option, to declare your route separators, like
options: { segment_separators: ['/'] }
But now, it is out of use, and i'm searching the way, to make pretty routes, like:
category:
pattern: /category+{cat}+page{page}
defaults: { _controller: MyPrettyBundle:Category:index }
And now i get this error:
No route found for "GET /category firstcategory page1"
404 Not Found - NotFoundHttpException
1 linked Exception: ResourceNotFoundException
As you can see, '+' is just cutted out of required route.
Any ideas how can i overcome this nasty error?
Fix issues with url decoding!
For URL encoding the + character is used to encode spaces. The URL is decoded before it's parsed, so to use actual + characters in the URL you would have to encode them as %2B:
/category%2Bfirstcategory%2Bpage1
That's not pretty, so using + as separator is not a good idea.
I'm trying to make a route parameter match an alphanumeric value that's 3 to 15 characters long. Code looks like this:
TestBundle_new:
pattern: /message/new/{name}
defaults: { _controller: TestBundle:Message:new }
requirements:
name: [a-zA-Z0-9]{2,15}
Unfortunately routing.yml fails to load. I was wondering if there is anything I can do to make this work?
You need to add quotes around your pattern.
name: "[a-zA-Z0-9]{2,15}"