@@ -278,18 +278,13 @@ Reverse routing allows you to define the controller and method, as well as any p
278278to, and have the router lookup the current route to it. This allows route definitions to change without you having
279279to update your application code. This is typically used within views to create links.
280280
281- For example, if you have a route to a photo gallery that you want to link to, you can use the ``route_to () `` helper
282- function to get the URI path ( route) that should be used. The first parameter is the fully qualified Controller and method,
281+ For example, if you have a route to a photo gallery that you want to link to, you can use the ``url_to () `` helper
282+ function to get the route that should be used. The first parameter is the fully qualified Controller and method,
283283separated by a double colon (``:: ``), much like you would use when writing the initial route itself. Any parameters that
284284should be passed to the route are passed in next:
285285
286286.. literalinclude :: routing/029.php
287287
288- .. note :: ``route_to()`` returns a URI path for the route, not a full URI path
289- for your site. If your **baseURL ** contains sub folders, the return value is
290- not the same as the URI to link. In that case, you need to use :php:func: `site_url `
291- like ``site_url(route_to(...)) ``, or just use :php:func: `url_to ` instead.
292-
293288.. _using-named-routes :
294289
295290Using Named Routes
@@ -304,11 +299,6 @@ with the name of the route:
304299
305300This has the added benefit of making the views more readable, too.
306301
307- .. note :: ``route_to()`` returns a URI path for the route, not a full URI path
308- for your site. If your **baseURL ** contains sub folders, the return value is
309- not the same as the URI to link. In that case, you need to use :php:func: `site_url `
310- like ``site_url(route_to(...)) ``, or just use :php:func: `url_to ` instead.
311-
312302Routes with any HTTP verbs
313303==========================
314304
0 commit comments