CodeIgniter is a widely used PHP framework that aims to help developers write better structured code and remove boilerplate tasks from the workflow. In this article, I'm going to explain some incredibly useful techniques to use when developing applications using CodeIgniter.

They cover things like setting up easier configuration parameters, optional config settings, creating HTML emails, application versions and separate response formats.

One of the powerful features of an IDE like Eclipse is the ability for it to "read" your code and give you some assistance about your API as you type. This could include things like class property or methods names, constants, functions, argument lists, and so on. Eclipse/PDT and ZendStudio do this by parsing a PHP class directly, but they also look at your docblocks and some other special comments where the raw PHP is not enough. This article is a bag of tricks that help you get the most out of code assistance using Eclipse/PDT or Zend Studio in those awkward corners of your code that you might have through previously inaccessible.

Among his tips are things like adding "@var" declarations to help with code completion, type hinting on methods/functions, using the "@property" annotation and using a "this" trick to override what class the IDE sees as the local object. ,/p>]]> Thu, 01 Dec 2011 12:55:32 -0600 http://www.phpdeveloper.org/news/15880 http://www.phpdeveloper.org/news/15880 In this new article on PHPBuilder.com today, they share ten handy tips that you might not have known you could do with the phpMyAdmin tool.

Despite approaching its 12th birthday, phpMyAdmin is still under active development, with at least one significant version released every year since the project's inception. In fact even after almost a decade of use I still marvel over discovering features which I had no idea existed. In this article I thought I'd highlight 10 useful phpMyAdmin features which may have escaped you during your daily interaction with this fantastic utility.

Making the list of their ten tips are things like:

• Manage User Privileges
• Change the Theme
• Monitor Server Status
• Create PDF Relational Diagrams
• Use Your Native Language

Over the years I've come across some useful tricks in PHP that are not obvious, but are worth mentioning. This is not meant to be a comprehensive list of all the useful tricks that you can do with PHP.

The list of six includes:

• Count Characters in a String
• Use Single Quotes When Possible
• Use Arrays in Form Fields
• PHP Output Buffering

Most of the outlined problems and solutions are focused on testability, maintainability and other good code practices. If you are not familiar with them, I recommend read about them ASAP as there is big chance that you are doing those things described in this post and don't even realize how wrong they are. Believe me, you will soon find yourself a way better developer.

He also advocates splitting out logic and putting it into a model to make future enhancements easier (and make for cleaner code), avoiding the use of exit/die in your scripts and quick mentions of the includePaths setting in the application.ini file as well as things like addJavascriptFile/addStylesheet/addOnload.

The project includes an article on "PHP performance tips", which is bordering on being ridiculous. There are of course lots of blog posts with similar nonsense around the web, but since this is being endorsed by Google, it's fair to assume that people might take it at face value. That's unfortunate, as almost none of it is true. The PHP Team responded back with this message, wherein they refute the unfounded nonsense.

He notes that these practices aren't the best road to optimization and, depending on when they might be used, could be harmful to the development of the application. He also recommends XDebug if you really want to get to know where your application is struggling.

Lists are all the rave these days for bloggers. The reason is obvious, they require very little thought or research to create. So, in keeping with the current trend, here is my list of three lists never want to see again.

His list of three are posts that contain:

• 5,000 PHP classes and tutorials
• 50 new PHP tricks you didn't know, didn't want to know, and will get you fired if you ever use them on the job
• Top PHP Frameworks

Blog posts should be about real content, not just spitting back out something anyone could put together in ten minutes with a little copy and paste. As Cal puts it:

If you are using a new PHP class, CMS, framework, or have a new technique you want to share, share it. Write a blog post and tell me how or why it solved your problem; bonus points if you describe the problem that it solved. You are not adding to the conversation is you are just recapping what others have said.

Let's take a look at 10 useful, yet rather unknown RSS-tricks for WordPress. Each section of the article presents a problem, suggests a solution and provides you with an explanation of the solution, so that you can not just solve some of your RSS-related problems but also understand what you are actually doing.

Here's their list:

• Control When Your Posts are Available via RSS
• Redirecting WordPress Feeds to FeedBurner Feeds
• Insert Ads (or Anything Else) in Your RSS Feed
• Format Your Images for Feed Readers
• Provide Your Readers with a Feed for Each Post
• Exclude Categories from Your RSS Feed
• Display Any RSS Feed on Your WordPress Blog
• Use Category-Specific RSS Feeds
• List RSS Feeds by Category
• Get Rid of RSS Feeds the Clean Way

What follows isn't so much a PHP trick as a fix for something that really should work, but doesn't. Although the manual implies that the behaviour described below is specific to Zend Engine 1, all my tests were performed against Zend Engine 2.2, PHP 5.2.5.

His example compares making a new stdClass both with and without a reference on the it and var_dumps out the result. The method with the reference fails silently, however and isn't able to correctly assign it to the global. He recommends a work-around though - setting it directly to the $GLOBALS superglobal.

For tip #1

If you just put a debug() statement in, you will see hundreds of outputs and would not know which one belongs to the case you are interested in. My favorite solution to this problem is to use the Configure class as a toggle for showing the debug information.

For tip #2

This is a very simple one. To make your application configurable via a global config file, all you need to do is the following.

Both come complete with code examples.