ThinkPHP 集成FIREPHP
ThinkPHP 集成FIREPHP 呵呵
TP的调试真的很傻很难用,要想输出trace信息,条件如下: 1. APP_DEBUG 以及SHOW_PAGE_TRACE设置成true, 2. action 必须有视图 才行 在这里发挥了自己的想象终于把 firephp 集成进来了,哈哈哈,方法如下: [就是替换 ThinkPHP/Lib/Think/Core/Log.class.php] 类 把 FirePHP.class.php 复制到 ThinkPHP/Lib/Think/Core 目录中,修改如下方法: [建议将原有文件备份哦,此仅作测试使用] static function record($message,$level=self::ERR,$record=false) { if($record || in_array($level,C('LOG_RECORD_LEVEL'))) { $now = date(self::$format); self::$log[] = "{$now} {$level}: {$message}\r\n"; switch($level){ case self::DEBUG: FirePHP::getInstance(true)->trace($message, $level); break; case self::INFO: FirePHP::getInstance(true)->log($message, $level); break; case self::SQL: FirePHP::getInstance(true)->info($message, $level); break; case self::NOTICE: case self::WARN: FirePHP::getInstance(true)->warn($message, $level); break; default: FirePHP::getInstance(true)->error($message, $level); break; } } } 对于 SQL的输出,因为 ThinkPHP/Lib/Think/Db/Db.class.php 里面第128行 对 调试参数写死了, 必须将其 与 C('APP_DEBUG') 绑定,很费解,此处修改为 加一个自定义的,不与原有的相冲突..代码如下: if(C('APP_DEBUG') || C('LOG_RECORD_SQL')) 在配置文件里面做如下选项,即可: 'LOG_RECORD'=>true, // 进行日志记录 'LOG_RECORD_SQL'=>true, // 进行日志记录 'LOG_RECORD_LEVEL' => array('EMERG','ALERT','CRIT','ERR','WARN','NOTIC','INFO','DEBUG','SQL'), // 允许记录的日志级别 日志级别可以自增减 呵呵

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Article discusses late static binding (LSB) in PHP, introduced in PHP 5.3, allowing runtime resolution of static method calls for more flexible inheritance.Main issue: LSB vs. traditional polymorphism; LSB's practical applications and potential perfo

Article discusses essential security features in frameworks to protect against vulnerabilities, including input validation, authentication, and regular updates.

The article discusses adding custom functionality to frameworks, focusing on understanding architecture, identifying extension points, and best practices for integration and debugging.

Sending JSON data using PHP's cURL library In PHP development, it is often necessary to interact with external APIs. One of the common ways is to use cURL library to send POST�...

An official introduction to the non-blocking feature of ReactPHP in-depth interpretation of ReactPHP's non-blocking feature has aroused many developers' questions: "ReactPHPisnon-blockingbydefault...

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.
