News Feed
Jobs Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

MaltBlue.com:
Using ZFTool for Basic Project Management
June 17, 2013 @ 11:18:42

Matthew Setter has posted a new tutorial about using the ZFTool functionality of Zend Framework v2 for managing your project's settings and configuration.

Welcome to another tutorial. Today, I will be giving you a walk through of zftool, which provides basic tooling support in Zend Framework 2. If you're new to Zend Framework, or have been reading the introductory series here, it can come in quite handy. But unlike other frameworks, such as Yii (through yiic) and Symfony (via the Command Line tool), the tooling support in Zend Framework 2 is rather light on. These respective tools provide rather robust support for automatically generating models from database connections, checking logs and a host of other much required functionality.

He shows you how to do a few things with the ZFTool - create a new project, make some modules inside it, build an autoloader classmap and check the installation with some basic diagnostics. Command examples and configuration samples are included in the post to help you along.

0 comments voice your opinion now!
zftool zendframework2 tutorial introduction project module diagnostic

Link: http://www.maltblue.com/tutorial/zftool-for-basic-project-management

Slawek Lukasiewicz's Blog:
PHP application diagnostics - Memtrack
November 08, 2011 @ 12:08:37

Slawek Lukasiewicz has posted about a handy tool that can be used to track memory consumption and performance in your PHP application - memtrack.

Application profiling can help us determine bottlenecks and possible problems during development. But sometimes we also need to diagnose problems in production environment. Frequent performance problems are connected with functions and methods using too much memory.

The tool allows you to set up thresholds for memory consumption and, if the scripts exceeds it, add warnings to your log files. He includes the simple instructions to install it (via PECL) and enable it in your php.ini. Some sample code to create a memory overvload is included to test it out. Configuration options let you set the limits and define functions to ignore if you know for sure there's trouble spots.

0 comments voice your opinion now!
memtrack extension diagnostic limit warning


Pierre-Alain Joye's Blog:
How to generate backtraces on windows without compiler
June 11, 2007 @ 11:08:00

In a new tutorial posted to his blog today, Pierre-Alain Joye shows how to generate backtraces on a Windows machine without the need for a compiler installed.

How to get a back trace on windows without having to compile PHP has been an impossible task for many of us. The difficulty was to first succeed to compile php (given that you have a visual C++ installed). If you are in the middle of a bug hunting session, no need to say that setting up a windows build system is the last thing you like, especially if it is your first time. Thanks to Edin's window binary and MS Diagnostic Debug , it is now possible to have a backtrace in a couple of clicks.

To use the method you will need a few pieces of software to help out but all are available for free. Next up are the steps to get things set up (simple) and the creation of the backtrace to catch the error, complete with screenshots for the whole way. The end result is a nice, pretty error message output to the browser (Internet Explorer) that also dumps the backtrace for you to use.

0 comments voice your opinion now!
backtrace windows compiler debug diagnostic tool screenshot backtrace windows compiler debug diagnostic tool screenshot


Zend Developer Zone:
PHP Security Tip #15 (Remove Temporary Files)
March 23, 2007 @ 09:20:00

The Zend Developer Zone has posted security tip #15 today, focusing on an easily forgotten aspect of web development (not just in PHP) - forgetting to remove temporary files.

As developers, most of us are very messy. I've worked on countless projects and at each either run across or left a trail of diagnostic files laying around. (info.php, test.php, doMe.php, etc.) These tiles, if found by someone with nefarious intent, can leak valuable information about your system.

Always remember to remove these types of files...as Cal puts it:

It would be a shame to spend all that time securing your application only to leave info.php or worse yet, a "quick piece of code" in test.php that could potentially leak dangerous information about your system. Don't help the ad guys any more than you have to.
0 comments voice your opinion now!
temporary files remove securitytip diagnostic temporary files remove securitytip diagnostic



Community Events











Don't see your event here?
Let us know!


symfony2 facebook application hhvm release framework hack introduction unittest composer component opinion install podcast performance security language package database overview

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework