Community News: WordPress 2.1.1 Dangerous, Upgrade
560242
Just in case you haven't heard yet and are running WordPress version 2.1.1 (that you've downloaded recently), you need to upgrade your installation because of a security exploit that made its way into the software.   From the WordPress Blog:   Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.   If you have even a doubt as to if you're running the bad version, go ahead and upgrade to version 2.1.2. Somehow, an individual gained access to the servers where the package is hosted and altered some of the code in the download file. This resulted in a method to bypass any security in place and allow the attacker full control.
576895
Here's what was popular in the PHP community one year ago today:Symfony Project: Book preview: read the Unit Tests chapterWebCheatSheet.com: Secure File Upload with PHPMichi Kono's Blog: The Best PHP Book Out ThereThe Bakery: Basic User Authentication in (CakePHP) 1.2.xPHPBuilder.com: Dynamic XML with PHPDavid Coallier's Blog: Zend_Db Without PDO part #3 (SVN Repository)?Community News: PHPLondon Conference 2007 AnnouncedMatthew O'Phinney's Blog: Overloading arrays in PHP 5.2.0Ilia Alshanetsky's Blog: 5.2.1 RC3 Released for testingJob Posting: Telio Telecom AS Seeks Senior Web Developer (Oslo, Norway)The Bakery: LightTPD and CakePHP setup in subdirectoriesJob Posting: Yahoo! Seeks Address Book Front-End Engineer (Sunnyvale, CA)HowTo Forge: PHP Programming BasicsJob Posting: Blue State Digital Seeks PHP/AJAX developer for politcal/tech consulting (Boston, MA)Zend Developer Zone:  AJAX Chat Tutorial Part 7 : Usability Improvements
366947
Lukas Smith is sending a wakeup call to the internet providers and web hosters out there - get involved in the PHP community!   We do not seem to have any ISP's active inside the PHP community. This is kind of odd, considering that PHP seems to be driving the business of hosters quite a bit. Why have none of them decided that PHP is important enough for their business that its worthwhile to ensure that their interests are taken into account?   He makes the suggestion of passing along the suggestion to bosses/co-workers/anyone who'll listen about getting involved. Suggested places to start would be as a part of the testers group or even contributing to the migration guide.
656053
PHPKitchen has an interesting post covering one of the banes of most web developers existance - the "back button problem".
155453
Popular posts from PHPDeveloper.org for the past week:PHPBuilder.com: AJAX and PHP Part 1Developer.com: Threads Versus The Singleton PatternNick Halstead's Blog: Google Gears Caching of WordPress in PHPDevShed: PHP, MySQL and the PEAR DatabaseDave Dash's Blog: Installing a PHP that can do symfony+doctrine on DreamhostChristopher Jones' Blog: Upgrade PHP with Oracle Application Server on LinuxPHP.net: PHP 5.2.3 ReleasedPro::PHP Podcast: Newscast for May 31st, 2007Secunia.com: PHP Integer Overflow Vulnerability and Security BypassPHPBuilder.com: PHP and Regular Expressions 101
519884
Marco Tabini (of php|architect) has posted some thoughts to his blog about the PHP4 end-of-life announcement and its relations to the current push to go PHP5 - mainly how it relates to hosting providers.   I'm sure that a large number are owners of small hosting firms - which, by far, provide the vast majority of PHP-powered websites that Netcraft carefully tracks for us - that sell cheap shared hosting. [...] If you provide shared-hosting plans, it's likely that your servers are still running PHP 4. Upgrading to PHP 5 is a logistical nightmare for two reasons: first, you don't necessarily know that you'll be able to properly set up and secure your systems; second, you don't know that your customers' applications will keep on running.   Both reasons can cause very different kinds of hassles for the hoster, especially when it comes to their customers. As Marco puts it "hell hath no fury like a customer scorned". When things are going smoothly, everything's good, but the second that you try to explain that the update is what's good for them, all they see are things breaking and freak out.   He suggests only one real solution - make the move and tell the customers now that things are changing. Help them all you can (with information about updated software and resources) but ultimately it's up to them to make the change.
550731
Evan Sims has posted some of his first impressions on the latest version of one of the most popular pieces of PHP blogging software on the web - WordPress 2.3.   So as many of you are certainly well aware, the long awaited Wordpress v2.3 was released today after a long series of betas and release candidates. 2.3 has had the blogging community foaming at the mouth for one reason: tags.   He spends a bit explaining what these tags are and what they're useful for before getting into the actual experience with the new update. He talks about issues he came across (updating/replacing plugins with ones of the new version) and the updates he needed to make to his theme to allow for his customizations to still work as planned.
676865
Ben Ramsey has posted a (quick) new items over on his blog that looks at solving two problems he was having with his blog - the now non-functional Flickr feed and a sorting problem with array_multisort.   I recently upgraded a few things around here (in particular, an upgrade to PHP 5.2), and I noticed two issues that occurred after the upgrade. [...] I easily solved both of these issues.   The correction to the Flickr feed involved changing the namespace information for his request (adding a trailing slash) because the SimpleXML functionality got a bit more particular about the format.   The problem with array_multisort involved adding in a parameter that was implied in previous PHP versions, SORT_STRING, to get his code correctly working.
42081
Blog: Popular add-ons could have their update process hijacked by man-in-the-middle attacks.
767454
PHP Magazine has a new posting today about an article from WebProNews.com concerning a new article - Generate HTML Files With PHP To Reduce The Server Load.
644334
WikyBlog is a scalable CMS/Groupware application with an AJAX enhanced tabbed interface enabling users to view/edit multiple files within the same page.   Version 1.4 adds the Wanted Pages, What Links Here, Orphaned Files and Dead-End Files special pages. Automated tasks have also been introduced to maintain database integrity and maintain Trash. A number of other improvements and bug fixes have also been made.  WikyBlog Home:   http://www.wikyblog.com     Get WikyBlog:   https://sourceforge.net/project/showfiles.php?group_id=148518&package_id=163821     WikyBlog Features:   http://www.wikyblog.com/Help/en/WikyBlog/Features
423195
Latest PEAR Releases:System_Folders 1.0.0HTML_QuickForm_DHTMLRulesTableless 0.2.3HTML_QuickForm_Renderer_Tableless 0.4.3XML_Query2XML 1.0.0Structures_BibTex 0.3.0Auth 1.4.3Text_Wiki_Creole 0.0.1Image_Tools 0.4.2Services_Pingback 0.2.1File_HtAccess 1.2.0Console_Getopt 1.2.1Testing_Selenium 0.3.0Net_MPD 0.3.0devMP3_IDv2 0.1.1Net_DNSBL 1.2.0beta1
661790
If you're both a WordPress an Mint user and are wanting to integrate them the easy way, check out this new entry from Chris Hartjes about combining the two.   Now, the installation is fairly easy but there was a weird bug that was appearing, where a check to see if you are running a licensed copy of Mint kept getting triggered when I tried to access my feeds via a feed alias. The solution? An ugly hack, if you ask me.   The problem was with a Pepper for Mint called Bird Feeder Pepper that helps track RSS feed usage. The solution he found was a snippet of PHP code you'll need to insert into several of the feed scripts WordPress offers (as provided).
179571
Here's what was popular in the PHP community one year ago today:Splitbrain.org: Add comments to any PHP scriptRyan Malesevich's Blog: Separate Trackbacks from Comments RevisitedDeveloperTutorials.com: Inserting An Array Into A DatabaseSymfony Blog: The Definitive Guide to Symfony and symfony 1.0 RC1 releasedSoledad Pendaes' Blog: PHP will never have a (real) Rails-like frameworkJSLabs Blog:  A web server in PHPRobert Swarthout's Blog: PHP frontend to Subversion (SVN)Christopher Jones' Blog: OCI8 1.2.3 Patch is Available on PECLDotVoid.com: Parsing the user agent string using PHPPaul Jones' Blog: Solar 0.26.0 Released, and New WebsitePierre-Alain Joye's Blog: Zip 1.8.5, small bug fixes releaseZend Developer Zone: Zend Monthly Newsletter - JanuaryMike Potter's Blog: Flash, Flex and PHP Just Got A Huge BoostJonathan Snook's Blog: Review: PHP SolutionsOracle Technology Network: Creating an Ajax Process Using PHP and Oracle
534932
Blog: Database issues are hampering some upgrades to Adobe Photoshop Lightroom 1.1.
23541
This week's latest PHPBarnstormer has been posted.
369996
Felix Geisendorfer has a reminder from developers out there - "PHP 5.2.1 was an evil release":   While I was at php|works I heard a lot of people say how bad of a release 5.2.1 was and that I should stay away from it. Well I didn't take it to seriously at this point, but when I checked what version of PHP we are running on my client project recently it turns out it was 5.2.1.   They were seeing performance issues (database related) so they upgraded to the latest version, 5.2.4, and immediately saw a performance jump of forty to sixty percent and a much lower amount of CPU usage. Upon some further research, he found a certain bug in 5.2.1 that could have been the culprit.