Dave Dash's Blog: Fixing Broken PATH_INFO
676040
Dave Dash has posted about a method he developed, using a custom prepend file, to correctly obtain the PATH_INFO information for his server.   symfony and other applications rely on the server's PATH_INFO being set properly. Unfortunately, I use a nonstandard server that doesn't natively support CGI [...] but I can't figure out how to do a urldecode in my configuration.   To get around the issue, he created a file he prepended to each request (via auto_prepend_file) that took the value and urldecoded it to put it in another $_SERVER value.
184446
Tycho:  I don't know whose fault it is exactly, mine or theirs, but I won't be installing Vista anytime soon.  I would like some crazy shit to happen when I minimize something don't get me wrong.  I want my windows to go Waja-wajow(!) is possible.  But if there's a great reason to "trade horses midstream" or whatever the going metaphor is I haven't discovered it.
22372
Blog: Yahoo IM fixed after temporary problems
386298
Please replace the release with the following corrected version due to  multiple revisions.
767747
Jikes is a great compiler but they could really benefit from better project management.  This bug  has been open for greater than 3 years now with no resolution.  One of the developers sent me a *private* email (without commenting or closing the bug) this this could be fixed by avoiding the use of symlinks but wasn't sure. Of course this email was sent more than 2 years ago so I have no decent way of finding it.  Adding insult to injury is the fact that IBM won't let me comment on the bug without an account.  The only problem is that my account won't activate.  In a nutshell if you want to use incremental compile with jikes you need to specify relative paths not full paths.  For example if y ...
569899
By Julio Ojeda-Zapata, Pioneer Press, St. Paul, Minn.  Sep. 6--Dave Andrews knew something was horribly wrong when he couldn't open the digital-photo files on his computer. All those pictures of his kids were suddenly inaccessible, the Rosemount man recalls.
477851
In this final section I'll present some MIDI-specific troubleshooting tips, along with a brief description of the setup here at StudioDave, a few closing remarks, and of course some links to the Linux music-maker du jour.
559035
Michael Kimsal has posted a formal prediction that a patch, created by someone in the community, will emerge making it simple to bridge the gap between PHP4 and PHP5 applications.   Given the high number of shared hosts still running PHP4, the backwards compatibility issues going from 4->5 (yes, there are some!) and the new PHP4 "end of life" date (8/8/8), someone will likely find a way to make these run together, and possibly even charge money for it.   He suggests that many hosts out there would happily pay a sum to get this kind of functionally for their customers. It would provide a solution to customers who just don't understand the force towards PHP5 and would make them (and their PHP4 applications) happier.
184682
Microsoft has issued a formal fix for a problem in Windows XP Service Pack 2 that appeared almost immediately after the update&#39;s release.
743840
Chris Shiflett has posted his own recap of the (just passed) php|works conference up in Toronto over on his blog.   I've been traveling non-stop since php|works, so I haven't had a chance to reflect on the conference, what I learned, who I met, and things like that. (Zak has been doing a good job of this lately, and I'd like to follow his lead.) I've probably forgotten more than I remember, but this is my recap.   Included in the things he mentions are:  The people he was able to meet (like Joshua Eichorn and Sebastian Bergmann) The talks he gave ("Truth about XSS" and "Agile PHP Testing") His interview with Cal Evans of the Zend Developer Zone The PHP 5 Certification and Wez Furlong's "Not PDO" talk
539560
Blog: Computer failure blamed for temporary grounding of flights
620214
On Paul Jones' weblog today, there's a posting covering one of the banes of PHP life - form processing/handling.
763006
Update fixes crashes caused by incompatibility with hidden advertising app.
690580
On the Dotvoid.com blog today, there's a new post that shares some handy code to parse out information from the incoming user agent string for the visitors for your site.   Recently I experimented a bit with an Apache log file analyzer written in PHP. It's not all that difficult were it not for trying to parse the browser, or user agent, string. [...] For my purposes I don't care much for the operating system details. This is the result so far. I'm still not very satisfied but I thought maybe other people might be interested and maybe help out.   He provides the code in the format of an encapsulated PHP function that returns the product they're using, the version number of the browser and other various comments.
78807
Cal Evans came up against a problem earlier in his development work - issues when he was trying to get his old include path.   What you SHOULD get back is a string describing your old include path. If you get false, you have hit the problem I hit last night. I went so far as to recompile 2 difference versions of Apache thinking (almost correctly) that it was something that had changed in my Apache config files.   If you're one of the "falsers" out there, check out the rest of his post of his solution around the problem. His problem stemmed from his trying to reassign a php_admin_value (instead of php_value where the script could override it) setting, specifically the one for the include_path.    He also points out that Zend Framework users might keep an eye out for this problem too as the Zend_Loader package changes the include path at times.
320544
On Christmas day, after the potlatch subsided, I headed out for a run. When I flicked on my MP3 player, however, I heard ... nothing. Glancing down at the display of my Creative Nomad MuVo TX I saw an unwelcome message: "File system error." Grrr.
624384
At Fry's this afternoon, where I bought two 500GB Firewire drives. Which it turns out I needed because after I got home all three external drives attached to my desktop were reported as damaged beyond repair by the new Mac OS. Coincidence? Lucky that I had exactly the hardware I needed to dig out of the mess? Who knows!