Routing
contact
Matched route
Route Parameters
No parameters.
Route Matching Logs
Path to match:
/contact
| # | Route name | Path | Log |
|---|---|---|---|
| 1 | actualites_index | /actualites | Path does not match |
| 2 | actualites_new | /new | Path does not match |
| 3 | actualites_show | /{id} | Path almost matches, but Requirement for "id" does not match (\d+) |
| 4 | detail_actus | /actus/{id} | Path does not match |
| 5 | actualites_edit | /{id}/edit | Path does not match |
| 6 | actualites_delete | /{id} | Path almost matches, but Requirement for "id" does not match (\d+) |
| 7 | actusfront | /actusfront | Path does not match |
| 8 | actualites_all | /actualités | Path does not match |
| 9 | actualites_all_list | /actualités_list | Path does not match |
| 10 | admin | /admin | Path does not match |
| 11 | asso | /associations | Path does not match |
| 12 | commercant | /commercants | Path does not match |
| 13 | app_calendar | /calendar | Path does not match |
| 14 | conseil | /conseil-municipal | Path does not match |
| 15 | contact | /contact | Route matches! |
Note: These matching logs are based on the current router configuration, which might differ from the configuration used when profiling this request.