The Bakery: Clear the PHP4 warnings when working in eclipsePHP
12741
CakePHP users can find a quick hint from The Bakery today pointing out how to get ride of some of the warning messages when working with the framework in PHP4.   CakePHP - a great framework, but sometimes surprising to those who are used to programming with PHP 5. EclipsePHP spits out pages and pages of warnings when compiling towards a PHP 5 base, scaring new CakePHP converts.   The method involves performing a global search and replace on seven key strings to help them conform to the CakePHP standards. The warnings will "magically" disappear following.
733011
Felix Geisendorfer has a "quick hit" tip posted to his blog today on using HTML 4.0.1 in your CakePHP 1.2 installation.   This is just a little tip for those of you who dislike their xhtml to end up as tag soup and still prefer to send out Html 4.01 strict. Here is how to make all helper functions in Cake 1.2 output Html 4.01 compliant markup instead of xhtml.   The helper he's created just loops through the entire $tags array and does a replace on the greater-than sign to add a slash to make it compliant.
701641
Havard Eide is asking for your help in a new entry to his blog. He's looking for ways to speed up his development in Eclipse, specifically in the debugging.   There is one thing I do need over everything else: remote debugging. Having used Zend Studio for 3 years now it hasn't been the best editor ( I'd rather prefer PHPEclipse/PDT ) but the remote debugging facility is superb [...] Eclipse it has all the tools you need to develop with but the debugging is slow, way too slow!   He's looking for anyone out there that might be able to help him speed up the debugging on his Leopard-installed version of Eclipse ("So slow actually that I had to install Zend Studio 5.5 for whenever I have to debug a file...")
253381
Latest PHPClasses.org Releases:Nweb ImageLeast Squares FitCalendar CalculationsParagraphGDColorSimple EnumerationFile Exchange ProtocolFind dateNaf_ValidatorGeneric Form classMulti Threaded Daemon
127648
Latest PHPClasses.org Releases:AShellPassword Generator & CheckerBPT_SessionManagerSubmit SecurityFTP Folder Copy or DeleteOcheck classIniInteractionBPT_LoggerPostgreSQL Backup and RestoreXML2Array_xmlreaderClaseDateTimeManagerPDO_EXTpopupMsgClase DateTimeManagerLiveValidationPHP
729779
The Tiger Heron blog has a new post from Tony Freixas looking at some of his experiences working with PHP in the Eclipse editor (including a mini-installation tutorial).   In my last article, I talked about installing PHP. With PHP installed, you will want to start writing code, so today's article is about developing PHP using the open source Eclipse integrated development environment (IDE).   He talks about what the Eclipse software has to offer before getting into the download and installation part of the tutorial. He goes all the way through - from configuration out to creating a sample PHP application (and debugging) with the software.
453805
From Iain Dooley on WorkingSoftware.com.au today, there's a new tutorial covering the installation of PHP4 and PHP5 onto a FreeBSD server.   So, briefly here is my little recipe for getting PHP4 and PHP5 to run concurrently on FreeBSD using Apache 2.2 and mod_proxy.   He points out one method that's been posted to get this all working, but notes that there are a few issues he found with it. That's the point of this post - to rectify and solve those problems to have you on your way to a happily working PHP4/PHP5 installation.   His guide is broken up into the key steps:   Compiling with mod_proxy from FreeBSD ports Installing another Apache instance  PHP Installation  Configuring and running Apache and a bug, Bug 37770, he came across where the proxy would just stop working
27208
Latest PHPClasses.org Releases:Adventure-(PHP-)FrameworkOhloh APIdm.KittenAuthuserManagerImage TransformSimple error handling classPHP Tree GraphPHP5 Calendarb3rtCSVReaderb3rtCSVWriterCRUD Class
719917
Latest PHPClasses.org Releases:phpmmPHP Array to JavascriptDay IteratorFile Reader and Writer AbstractionDirectory and file infoSimple PagerSimple ListScript timerMessage HandlerText 3DWindowFXLake effectWPGetYahoo Messenger PM send via PHP
45094
The Bakery has a new CakePHP tip posted today showing how to improve the unbindModel handling on the model side of things (versus in the controller as mentioned previously).   The problem with that solution is that it requires you to change the way you define your model relations. [...] Rather try to change your code to suit your needs, and let CakePHP do what it does best: act as a framework.   The technique approaches the associations differently - loaded and called when you make the call to expects() versus just automatically. They include the code to make it all work for an extension to the Model (AppModel), and extension to the AppModel (Title), and finally the TitlesController that shows the deliberate calls to expects to pull in the models.
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.
584290
Andrew Johnstone has posted some of his experience he's had developing with one of Zend's latest offerings - Zend Neon. Neon is the Zend project to bring robust PHP development functionality to the community on top of the Eclipse platform.   I've been using Zend Studio for Eclipse (beta) for several weeks in a rewrite of a framework and numerous sites at work and overall I really like the IDE. Its got some great features and being based on the eclipse project makes it really extensible and customizable.   He happy overall with the IDE but has come across some bugs in his time developing in it (nine of them) with issues ranging from the SVN functionality and samba out to small syntax sorts of things (like the auto-formatting).
740094
In his travels as a PHP developer, Jamie Wong has gathered some helpful debugging tips that are shared in this latest post to his blog.   Here are some bugfixing rules and tips Iâve learned working all these years with PHP. I emphasize mostly on fixing bugs than preventing them, which is another subject worth of its own article. Iâve moved to Rails, but I wanted to finish this post as a farewell and thanks to every article and documentation that was useful to me. Hope this is useful to you too.   Topics covered include:  Assume nothing Turn Error Reporting to show all errors Read the error message Understand the bug "Scooby-Bug, where are you?" Get as much information as possible  Each has some explanation below it and, in some places, a bit of code to clarify the point.
629310
You cannot help but like someone like Greg who is honest and humble:  "I am one of the core developers of the PEAR package who has joined the game relatively late... The base PEAR class is one monstrous mistake, and PEAR_Error is pretty close. Everyone knows this. I designed an error class that is much, much more flexible and it is part of PEAR 1.3.1 (PEAR_ErrorStack) - check it out. "  Sadly it's just not true that everyone knows that PEAR class is big mistake (Jeff Moore has more on why PEAR.php is awful).  Given that PEAR is both an important framework and a worthless class, the confusion in names will  definitely  cause the value of the PEAR class to be overestimated. Just read any article on PEAR and you can see what nice words they have to say about the base classes :-(     I once said once that too many PEAR developers were journeymen. This might have offended  some people, but I was trying hard to be diplomatic. I must say that today the PEAR group is definitely more mature, and they have learnt a lot about library design. What would really make my eyes light up  would be an PEAR2 initiative that kept the existing classes, but dropped the bad seeds such as PEAR.php (e.g. the PEAR and PEAR_Error classes).   And in case you were wondering, I do think there's great value in the PEAR DB API. API's are important for interoperatability. For example, ADOdb has a PEAR DB compatibility mode. I would certainly be flattered if PEAR DB had an ADOdb compat mode too :-)
632471
Latest PHPClasses.org Releases:URI CacheEnTransliterationHtmlCreate CSVText Helper ClassLista Paginacao ClassshagaConfiguratorldap_classBrute ForceMulti-thread SimulationiCaptchaFAPDFID3Tiny P2P
267028
In the new blog entry, Jonathan Snook shows how to implement "conditional content" on your CakePHP application.   I finally got around to implementing conditional content here on Snook.ca. I've wanted to do this since I moved to the new design just over a month and a half ago. [...] With a little bit of late night development and some quick help from Larry (aka PhpNut, the lead developer of CakePHP), I've developed what I have dubbed "Elemental".   In his example he shows the two parts making up the functionality - the controller with new methods (in app_controller.php) and a new helper called "Elemental". Using the methods enableElement and disableElement you can turn off and on different chunks of code that are stored in an element array.
217574
As mentioned by Ed Finkler, there's a list of signs your PHP needs refactoring from Soledad Penades.    I have had to go through a php application recently which has given me more than one headache and has required me to use all my possible patience. While working with it, I thought This is good material for an article, so that nobody else does the same in the future, and nobody else will need to experience the same displeasure as I have had to.   So here are the signs your PHP application needs a serious refactoring, right now    Included in the list are things like:   Uses global variables Everything's an array The neverending switch Interface inconsistency   It hits on one of the thing that bugs me too, the problem of "Brackets galore" - so many subarrays that you have to resort to three or more sets of bracketed keys to get to the value you want. It's bad enough trying to follow someone else's code without having to "trace down" an array to figure out which of the values they're talking about.