1. Open http://frontend.cmcp-api.localhost/ in the browser. A debugger toolbar appears at the bottom of the page and can be expanded by clicking, as shown in Figure 1.
2. In Postman, make a GET request to http://www.cmcp-api.localhost/v1/pages. It returns a 200 response, but no debugger toolbar appears, as shown in Figure 2.
3. Continuing from step 1, click the Yii logo on the debugger toolbar to open the available debug data, as shown in Figure 3.
4. The URL for the frontend application’s debugger is http://frontend.cmcp-api.localhost/debug/default/index, as shown in Figure 4.
5. Based on the analysis of the frontend application’s debugger URL, simply replacing frontend with www gives the URL for the API application’s debugger. Open http://www.cmcp-api.localhost/debug/default/index, as shown in Figure 5.
6. To view the debug data for the GET request to http://www.cmcp-api.localhost/v1/pages made in Postman, click the Tag link corresponding to the respective URL, as shown in Figure 6.
7. The Log Messages page contains the debug data for the GET request to http://www.cmcp-api.localhost/v1/pages made in Postman, as shown in Figure 7.
8. There is an error in the Log. Click to view it, as shown in Figure 8.
9. Referring to the URL https://www.shuijingwanwq.com/2018/01/10/2206/ , step 65 needs adjustment because ‘model/*’ is missing, as shown in Figure 9.
'i18n' => [
'translations' => [
'model/*'=> [
'class' => 'yii\i18n\PhpMessageSource',
'forceTranslation' => true,
'basePath'=>'@common/messages',
'fileMap'=>[
],
],
'app'=> [
'class' => 'yii\i18n\PhpMessageSource',
'forceTranslation' => true,
'basePath'=>'@api/messages',
'fileMap'=>[
],
],
'*'=> [
'class' => 'yii\i18n\PhpMessageSource',
'forceTranslation' => true,
'basePath'=>'@api/messages',
'fileMap'=>[
],
],
],
],
10. Make the request again in Postman, then reopen http://www.cmcp-api.localhost/debug/default/index. Select the latest record and click to enter; you will find that the error in the Log has been fixed, as shown in Figure 10.
