@@ -20,7 +20,7 @@ class ArticlesController extends AppController
2020
2121Now, let's add an action to our controller. Actions are controller methods that
2222have routes connected to them. For example, when a user requests
23- ** << www.example.com/articles> /index>** (which is also the same as
23+ ** <www.example.com/articles/index>** (which is also the same as
2424** <www.example.com/articles>** ), CakePHP will call the ` index ` method of your
2525` ArticlesController ` . This method should query the model layer, and prepare
2626a response by rendering a Template in the View. The code for that action would
@@ -44,9 +44,9 @@ class ArticlesController extends AppController
4444```
4545
4646By defining function ` index() ` in our ` ArticlesController ` , users can now
47- access the logic there by requesting ** << www.example.com/articles> /index>** .
47+ access the logic there by requesting ** <www.example.com/articles/index>** .
4848Similarly, if we were to define a function called ` foobar() ` , users would be
49- able to access that at ** <www.example.com/articles> /foobar** . You may be tempted
49+ able to access that at ** <www.example.com/articles/foobar> ** . You may be tempted
5050to name your controllers and actions in a way that allows you to obtain specific
5151URLs. Resist that temptation. Instead, follow the [ CakePHP Conventions] ( ../../intro/conventions )
5252creating readable, meaningful action names. You can then use
@@ -120,7 +120,7 @@ When specifying URLs in CakePHP, it is recommended that you use arrays or
120120leverage the reverse routing features CakePHP offers.
121121
122122At this point, you should be able to point your browser to
123- ** < http://localhost:8765/articles > /index** . You should see your list view,
123+ ** < http://localhost:8765/articles/index > ** . You should see your list view,
124124correctly formatted with the title and table listing of the articles.
125125
126126## Create the View Action
0 commit comments