Hi,
at first you should post the code in question, so in your case the whole
link_to-statement.
>From your posts it seems you're mixing things up a bit.
When using link_to (or url_for), you either use the name of the routing
(e.g. employeerecord, and add an @ in front of it), or you use the real path
without the add. So, for example, you either
echo link_to('@employeerecord');
or
echo link_to('/default/index');
In your second post you seemed to have a spelling mistake as in the first
post there is only a "addnewemployee", no "addemployee".
Finally, a short sidenote: From your routing things seem a bit mixed up. In
generell, if you have an employee-object, it's a good thing to capsulate
this object in one module (normally employee), and have a add-action,
overview-action etc. and then routing whatever url you like to this module
and the appropiate action. Just have a look at the jobeet tutorial where
this structure is promoted and you get a feeling of how to handle things in
symfony.
Have fun,
Sebastian
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
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
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
