| Issue 400: | Enhance web log route | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Currently, web log route is not nice when dealing with fragment page response (mainly ajax response) because the response may be treated differently. Turning on showInFireBug does not always work. We propose to use response header to record log messages and on the client side, we run a special piece of js that can extract the messages from the header and display them in js console. |
||||||||||||||
,
Jul 25, 2009
To solve issues with ajax I would propose to check for ajax request: http://snipplr.com/view/1060/check-for-ajax-request/ protected function render($view,$data) { if (Yii::app()->request->isAjax()) return; ... } |
|||||||||||||||
,
Sep 10, 2009
@pestaa: could you take a look at this one? Feel free to postpone this if you don't have enough time. Thanks.
Owner: pestaa.hu
|
|||||||||||||||
,
Sep 29, 2009
(No comment was entered for this change.)
Labels: -Milestone-1.1a Milestone-1.1b
|
|||||||||||||||
,
Oct 28, 2009
@wei: any idea on how the client side js should be written?
Cc: weizhuo
|
|||||||||||||||
,
Nov 01, 2009
(No comment was entered for this change.)
Status: WontFix
|
|||||||||||||||
 Sign in to add a comment
|
|||||||||||||||
