There are a host of technologies and tools from Microsoft that can add value to your PHP solutions, save you time, and are just plain cool. This presentation will cover server technologies like FastCGI, IIS and the PHP SQL Server Driver, client technologies like the ASP.NET AJAX Library and Silverlight, as well as developer tools. This is not a sales pitch – it’s a technical walkthrough with demos, and will give you pointers to lots of resources for digging deeper.

I’m sure Glen’s talk will be interesting, and I’m looking forward to a chance to catch up on the current state of web servers in Microsoft-land. While I tend to use unix-based systems for most of my own work, there are plenty of organizations who are standardized on Microsoft products, and you have to be able to be able to work with what they have. Case in point, my wife is hoping to set up a WordPress website for her department at work, and they’ll probably set it up on a Windows-based server.

If anybody reading this is planning to attend, please introduce yourself. I’ll be wearing a WordPress shirt.

ShareThis

And on that note, I’ll mention that Internet Explorer 8 Beta 1 is available for download. Go break the web!

ShareThis

But waitaminnit… What’s this stuff about forward compatibility by adding some new X-UA-Compatible header to my pages or my server? Am I reading this right? Are you telling me that in order for IE8 to use its fully compliant rendering, we have to add something new to our pages? And that if we don’t, it will fall back to rendering pages just like IE7? Is that what this means?

That’s just dumb.

Screw their stupid “don’t break the web” motto. Break it! Break the web in the name of progress! How will we ever move forward if you keep dragging us back? And while you’re at it, quit trying to misdirect us with that “don’t break the web” nonsense. Putting out a browser with excellent CSS support is not “breaking the web”, it’s fixing it! There’s no real shame in putting out a better product, and admitting that the previous versions had flaws. This is a concept called “continuous incremental improvement”.

There has already been a lot of reaction from the web development community. There are several big names behind the idea. There are several big names against it. I’m not a big name, but I fall in the latter camp. This is not “forward compatibility”, it’s not “forward” anything. This is keeping progress of the Internet Explorer browser and adoption of better standards at a crawl instead of letting them make an evolutionary jump.

Oh, and unless I’m missing something here, there was already a mechanism in place that the IE team has already encouraged web developers to use, which could do the same job: conditional comments. What’s that? Oh yeah, there are problems with that, too.

If you need more reading material on this subject, check out Mark Pilgrim’s links. At the time of this writing, he has pointers to 29 articles, and I’m sure there will be more.

ShareThis

WeLoveWP.com highlights great looking WordPress sites, and it’s powered by WordPress, too!

From time to time, someone will hear that I’m involved with WordPress, and ask me a few questions about it. Some people already have a WordPress-powered site (either self-hosted, or on wordpress.com), and some have never actually used it, but they’ve heard of it. Often, they just want me to show them a WordPress site, so they can see what it looks like. Occasionally, someone will ask whether any big companies or famous people use WordPress. And one thing I often hear is along the lines of, it just does weblogs, if I have a business site, I’d want to use something else, right? But in reality, WordPress is an excellent tool for managing a business site. When I tell people this, they’ll often ask me for some examples of non-blog sites using WordPress.

So I end up searching for old bookmarks, looking through my feed archives, and checking the Codex until I find some suitable choices. Likewise, if someone just wants to see some examples of WP sites, I want to show them something that really stands out.

Now I’m finally going to document a really nice selection of sites that I can point them to for several examples, a sort of “Best of WordPress”. Some sites just look good. Some are examples of famous celebrities, companies, or organizations. Others showcase WP in a non-blog capacity. In no particular order, here is my list of Awesome WordPress Sites:

• Alex King’s Crowd Favorite not only has great design, but is a perfect example of using WordPress to power a business site.
• And Crowd Favorite, in turn, is responsible for All Things Digital, which is powered by WordPress-MU. Alex also has a great series of articles about building a customized WP site.
• ChickSpeak is another WordPress-MU site, with a focus on women’s issues. It’s structured more like a social network than a blog. There’s an article outlining ChickSpeak’s development that’s interesting, as well. via: photomatt
• If you grew up in the eighties like my wife and I, then you can remember when musician Thomas Dolby was blinding everybody with science.
• CNN’s Political Ticker blog is a WordPress.com VIP Hosting site.
• Robert Scoble’s Scobleizer blog is another WordPress.com VIP site. Scoble has been an icon in weblog circles for many years now, and is famous for his prolific output, as well as for being an author and a former Microsoft technical evangelist .
• Yodel Anecdotal is Yahoo’s corporate blog.
• delicious:days is a food blog that looks good enough to eat. Simply beautiful.
• NASA Ames Research Center is powered by WordPress. This group is responsible for many of NASA’s cutting-edge research projects.
• PlayStation.Blog is the official PlayStation blog from Sony U.S.
• Nancy Pelosi, the first female Speaker of the House, has a blog called The Gavel. WordPress is in ur guvrnment blogging ur lejislashun!
• Ford Motor Company’s Global Auto Shows site doesn’t look much like a blog, but it’s all wrapped up in WordPressian goodness.
• CSS Remix is a showcase of sites with
  great design. And the site itself looks schweet.
• welovewp.com highlights many WP-powered sites. Some are business-oriented, some are more standard blogs, but all of them have really great design. Oh, and of course, welovewp.com is powered by WordPress, as well.

Of course, the sites I’ve listed here are only the tip of the iceburg. There are tons of fantastic WordPress sites in the wild that deserve as much attention as these. Do you know of some? Post them here, and whenever somebody asks you about great WordPress sites, you can just give them a link to this post!

ShareThis

#...assume that we declared %hash,
#   $foo, $bar, $baz, etc previously...
$hash{'foo'} = $foo;
$hash{'bar'} = $bar;
$hash{'baz'} = $baz;
# ...ad nauseum...

Surely, there’s a more elegant way to do this, right? Of course there is. The mantra of perl programmers is TMTOWTDI (There’s More Than One Way To Do It)! The first and most obvious approach that comes to mind is to use “variable variables”, technically known as “symbolic references”:

my %hash;
my @vars = qw(foo bar baz);
foreach my $var (@vars) {
  # This uses a symbolic reference. When $var is 'foo',
  # then saying $$var is like saying $foo.
  $hash{$var} = $$var;
}

The problem is that symbolic references are frowned upon, and will cause perl to get angry with you if you’re running with use strict (as you should be). You can get around this by declaring the scope of $foo and friends as ‘our’ instead of ‘my’, and by using no strict 'refs' inside the foreach loop. I’m pretty sure that this wouldn’t cause any memory leaks, but it’s still an iffy solution because you have to change the scope of a bunch of your variables to ‘our’, which might have undesired side-effects.

The next refactoring is a nice improvement. The main difference is that it requires you to stick your list of values into a temporary array. Just keep in mind that this array will be modified (emptied) in the process:

my %hash;
my @keys = qw(foo bar baz);
my @values = ($foo, $bar, $baz);
foreach my $key (@keys) {
  $hash{$key} = shift @values;
}

Ah, much better! No problems running strict, and not too ugly. A final improvement, suggested to me by David Narayan, is to use a hash slice:

my %hash;
my @keys = qw(foo bar baz);
my @values = ($foo, $bar, $baz);
@hash{@keys} = @values;

That’s about as succinct as it’s going to get. The only disadvantage here might be if your list of key/value pairs was large, this would probably use a lot of memory. In that case, you’d probably want to use the foreach loop, as in the previous example.

ShareThis

The goal of the WordPress Object Cache is to provide a way to persistently store results from expensive queries in an external cache file. This lets us avoid re-querying the database or re-fetching information from an external web service if we think that the data hasn’t changed. It should be noted, however, that some server environments have trouble using the cache. It is up to you to monitor your server to determine whether use of the cache will benefit your sites,

Using the object cache is actually quite simple. You write data to the cache using wp_cache_set(), and you read cached data with wp_cache_get().

Before I get to the sample code, there are some other things you’ll need to check. The object cache is disabled by default. In order to enable it, you’ll need to edit your wp-config.php file. Add the following lines, after the setting for WP_LANG:

// Enable the WordPress Object Cache:
define(ENABLE_CACHE, true);

Also, make sure that there is not a define for a DISABLE_CACHE constant. In addition, you will need to make sure that you have a wp-content/cache subdirectory on your host, and that it is writable by your web server process. I assume that if you are planning to write code to use the object cache, that you know how to handle this on your host server.

That said, let’s take a look at how you use the wp_cache_get() and wp_cache_set() functions in your own code. First, we’ll examine how we put data into the cache. Think of the cache as a set of containers, each of which can store several data packets. You can name the containers and the packets within, so that you know how to retrieve them later. In these examples, I am naming the container mycache, and we’ll call the data packet mysettings. It would probably be a good convention to name your own container based on the name of your plugin, and name the packets based on what kind of information you are storing (e.g. userdata or popularpostinfo).

Here’s how we write data to the cache:

  // Whenever we need to rewrite the cache data:
  // This could be calling a database, webservice, etc.
  $mydata = my_complicated_data_query();
  $myexpire = 60 * 60 * 24; // Cache data for one day (86400 seconds)
  wp_cache_set('mysettings', $mydata, 'mycache', $myexpire);

You’ll have to determine the best point in your code to do this depending on what kind of data you’re caching. For example, if you are caching user profile data, you might want to update the cache anytime a user’s profile changes by hooking into the profile_update() API hook.

Now, when you want to avoid that complicated database query, check the cache first. If your information is not already in the cache, or if it has expired, wp_cache_get() will return false. In that case, you’ll need to re-query the database for the information. Otherwise, it will return whatever data structure that you previously stored.

  // First of all, before you try to access the user data, check
  // the cache.
  $mydata = wp_cache_get('mysettings', 'mycache');

  if (false === $mydata) {
    // The cache data doesn't exist or it's expired.
    // Do whatever we need to populate $mydata from the
    // database normally... 

    $mydata = my_complicated_data_query();

    // Since we know that the cache isn't up to date, we should
    // write this fresh information to it now, so that we can avoid
    // the query next time.
    $myexpire = 60 * 60 * 24; // Cache data for one day (86400 seconds)
    wp_cache_set('mysettings', $mydata, 'mycache', $myexpire);
  }

It’s up to you to decide an appropriate amount of time to cache your data and to determine which API action hooks should trigger cache updates. A whole day will be too long for some types of information. But with this basic information in hand, it should be relatively easy for plugin authors to take advantage of the object cache.

ShareThis

Bob smiles and replies, “we can have your car ready by noon on Friday, and it will cost $200.” Alice says that this is acceptable, and leaves her car to be worked on.

On Wednesday afternoon, Bob talks to Charlie, the mechanic. “How are you progressing on Miss Alice’s repairs?” Charlie gives Bob a blank look.

“I gave it a quick look yesterday, but I haven’t even started working on her car. I’m still finishing up the work on Mr. Durham’s truck.”

“Haven’t started? We have to get her car working by Friday at noon!” Bob exclaims.

Charlie narrows his eyes and shrugs. “That’s not going to happen. I had to order some parts, and they won’t even be here until tomorrow.”

Bob gives Charlie a pained look and sputters, “surely you realize that Miss Alice is an important customer? She works for a company that has a fleet of leased cars, and they get all their servicing from us. If we don’t have her car ready on time, we could lose that contract!”

Charlie looks back and Bob and replies, “Maybe you should have thought of that earlier. And maybe you should have asked me what my repair schedule looked like before you gave her an ETA on her repairs. Better yet, you probably should have asked Dave, since he’s the shop manager. But, no — you ignored our normal workflow, and now I’m going to have to work overtime because of your mistake. And when this lady gets her car back, if everything works fine, she’ll send you a nice thank you note, and the shop owner will congratulate you. But if I make a mistake in my hurry to meet your unreasonable deadline, you’ll blame me, and the shop owner might fire me. Is that basically right?”

“Yup.”

“I guess I’d better get to work, then.”

Software Australia Buy software online in Australia

ShareThis