In a response to this post on the PHP 10.0 Blog, Richard Heyes offers a method for what Stas was wanting:

OK, then what we do if something weird happens in production and we want to see the errors, but we don't want others to see them? [...] Maybe PHP could have some setting like display_errors=local which would enable display_errors for requests originating from developer machine but would disable it when outsider accesses it?

Richard's solution checks the HTTP_HOST value of the current request and, based on whether it's marked as "live" or "dev", uses a ini_set to change the display_errors setting to true/false.

The PHPEveryDay.com website has several new tutorials they've posted recently - here's the list:

• PHP WDDX: Creating Web Service Client
• PHP WDDX: Creating Web Service Server
• PHP WDDX: Unserializing Data
• PHP WDDX: Complex Serialization
• PHP WDDX: Simple Serialization Using PHP function
• PHP WDDX: Recordset Element
• PHP WDDX: Struct Element
• PHP WDDX: Using Array Elements
• PHP WDDX: Understanding Simple Data Type
• PHP WDDX: Understanding Data Elements
• PHP WDDX: Understanding Anatomy of WDDX
• PHP WDDX: Introduction

Check out PHPEveryDay.com for even more great tutorials and articles.

In a new article from PHPBuilder.com.au today, they talk about the "powerhouse of web services", SOAP, and how to get started working with it in PHP.

You've tried your hand at building mashups, experimented with a few RESTful Web services, maybe even started your own. Sure, you've got data sharing working. But how do you make your Web applications really talk to each other? In this tutorial, I'll show you how to take your Web applications to the next level with SOAP.

They opt to go with the NuSOAP method to consume another service and create your own simple one. They include a few code examples for either side and a (very) brief look at doing some debugging with what NuSOAP has to offer. One thing to note - if you have PHP5's SOAP extension compiled in and working, NuSOAP will throw an error about redeclaring a class name. This is because of a conflict between the naming of the SOAP extension's methods and NuSOAP.

Raphael Stolt, with some time on his hands, set up a local copy of Xinc, the "shiny new Continuous Integration(CI) server" as hosted on the Google code site and spent some time working with it:

Since then the idea of building a Growl publisher plugin for Xinc was traveling my mind repeatedly, so the following post will break this circle and show a possible approach to build such a plugin, which can be used to notify the build result for continuously integrated projects and thereby provide an on-point/immediate feedback.

He includes the plugin class (ready for cut&paste) as well as the task definition and how to hook it all in to the Xinc build system. There's also a little example of it in action - a happy/sad indicator showing if the build failed or was a success, right there on the desktop.

On the Developer Tutorials blog today, Akash Mehta has posted the second part of his look at the "ultimate web development environment", a continuation from this previous part.

Today I'm going to look at a local development server and its PHP configuration, as well as some of the IDEs/editors available for Linux, especially the cross-platform options.

Tools mentioned this time include things like a local development server (invaluable) some PHP configuration tips and the editors they mentioned, things like Aptana, Eclipse and Zend Studio.

Korynn Bohn has posted a new tutorial/article on the Zend Developer Zone website that talks about (and advocates for) web services.

Web services are the coolest technology I know of that ends up turning everyone off. I don't know about you, but when I go to a lecture on Web services, invariably tons of acronyms come out [...] and then I start to nod off and dream about a land where free Krispy Kreme donuts grow on trees.

He reframes the web services world away from the acronyms and strict standards to more towards using it as a method of communication between apps, letting them engage in some friendly conversation. He uses the rest of the tutorial showing how to create an RSS reader of sorts using dashes of PEAR, XML, C#, XSLT, Ajax and Flex.

According to this post on the Zend Developer Zone website (a press release from Zend), they're classifying Windows Server 2008 as being certified "PHP ready".

This announcement is the latest in a series of collaborations between Zend and Microsoft aimed at delivering high performance and reliability for PHP applications running on the Windows Server platform. Several of these enhancements have been contributed back to the PHP community.

As a part of the project, Microsoft has even put effort into ensuring that several of the popular PHP packages (like Mambo and WordPress) work right out of teh box with a Windows Server 2008 installation.

Mike Willbanks has posted an introduction he's written up giving some helpful hints at tuning your servers and PHP applications for performance.

The focus of this post is not to show performance related items to specific PHP frameworks since many bottlenecks actually apply before running the framework itself that should certainly be solved up front. Therefore in this posting I attempt to look at simple items that can be deployed in order to produce finer tuned systems.

He talks about a few different aspects:

• PHP Performance Tuning (opcode caching, apc file priming, includes, loops, etc)
• RDBMS Performance Tuning (indexes in queries, query caching, archiving)
• HTTP Performance Tuning (content compression, css sprites, limit modules, etc)

Stuart Herbert has posted about a very helpful method server admins can use out there to not only help secure their server but possibly make their web hosting users more happy in the long run - using suphp on a shared server (security).

The challenge with securing a shared hosting server is how to secure the website from attack both from the outside and from the inside. [...] This has created a gap that a number of third-party solutions have attempted to fill. One of the oldest of these is suphp, created by Sebastian Marsching.

He works through the whole process - the installation (this is all on a Gentoo linux system), configuring for your Apache install, changing Apache to make it work with suphp and finally some benchmarks and parting comments concerning its use.

In the process of debugging one of his scripts, Brian Moon came across a default setting (and problem) in the MySQL extension that didn't seem to make much sense to him:

There are several reasons that PHP could not be able to connect to MySQL. [...] Or, perhaps the entire server is offline.

The mysql.connect_timeout setting in the php.ini is supposed to handle this sort of instance, but the default is set tpo 60 seconds. It's only apparently used when the server is completely offline and, in his opinion, is set way too high. He's proposing a patch to the MySQL extension to change this setting's default to shorten it to something a bit more reasonable.