I have recently been deploying a few wordpress sites, and I have to say that while I am not really a fan of PHP I love Wordpress. I always thought it was just a blogging tool, but it is so much more, a web site builder, a CMS, an online store, you name it Wordpress can do it, and if it can't there is a plug-in to make it do what you want.

One thing you will find after installing on IIS is that the permalinks do not work, and if you Google this problem you will find all kinds of complex solutions from creating custom 404 error handlers to using URL rewriters like ISAPI Rewrite and changing code in the core files. But guess what, you don't need any of this, the solution is in fact really simple.

On the permalinks page, choose the "custom" option and simply create your desired permalink and DO NOT put a trailing slash, e.g.

/index.php/%year%/%monthnum%/%postname%

Yep that's it, nothing else required. I have tested this on IIS 6 and IIS 7 with Wordpress 3.0 and 3.0.1, whether earlier versions of Wordpress will work I do not know so don't ask.

The only thing you should need url rewriting for is if you want to remove the index.php from the url and make it even more search engine friendly. If you do need these features with IIS 6 hen use ISAPI REWRITE or APE both of which support Apache Mod_rewrite rules, with IIS 7 Wordpress will generate the required rules for the built in url rewriter and you just paste them into your web.config, so nothing else required.

I was just asked to help someone troubleshoot a site that worked fine on previous host but didn't work on Windows Server 2008 / IIS7.  None of the images on certain pages were displaying,  the image path looked something like this:

http://www.sitename.com/subfolder/bin/file.jpg

The subfolder wasn't marked as an application, although that doesn't really matter.  The point is that since /bin/ was in the path somewhere, and it turns out that  IIS7 wont allow any file to be displayed with a /bin/ in the path.  It serves up a 404.2 error saying file or directory not found.

404 - File or directory not found.

The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.If you look

If you look in applicationHost.config you will find the following under the <requestFiltering> section:

<hiddenSegments applyToWebDAV="true">

  <add segment="web.config" />

  <add segment="bin" />

  <add segment="App_code" />

  <add segment="App_GlobalResources" />

  <add segment="App_LocalResources" />

  <add segment="App_WebReferences" />

  <add segment="App_Data" />

  <add segment="App_Browsers" />

</hiddenSegments>

So, IIS7 now blocks those key folders and doesn't allow them to be seen.  To the outside world, any page in any of these folders appears to not exist.

The easy solution is to change the folder name, but there may be times when you really do want to keep the path name, such as for SEO purposes.  Not to worry, it can be changed easily enough.  This setting in on purpose though as it is for asp.net, so you usually shouldn't remove it for the whole site.

If it is your own server then you can use AppCmd or do it manually from applicationHost.config or web.config.  Since requestFiltering is allowed to be set at the site or folder level by default, it's probably best to set a web.config file in the folder that you want to allow, which is your only option on shared hosting.

To do this on a per folder level, create a web.config file in your folder and type or paste the following into it.  It should look something like this:

<?xml version="1.0"?>

    <configuration>

      <system.webServer>

        <security>

            <requestFiltering>

                <hiddenSegments>

                  <remove segment="bin" />

                </hiddenSegments>

            </requestFiltering>

        </security>

      </system.webServer>

</configuration>

If you want to make the change to your applicationHost.config file instead, you can do it by adding a location tag to the bottom of the file (well, almost the bottom - along with the other location tags) like this:

<location path="sitename.com/subfolder/bin/debug">

    <system.webServer>

        <security>

            <requestFiltering>

                <hiddenSegments>

                    <remove segment="bin" />

                </hiddenSegments>

            </requestFiltering>

        </security>

     </system.webServer>

</location>

To do this using AppCmd just drop to the command prompt and type the following: (Be sure to change the paths to the correct page before running this.)

C:\Windows\System32\inetsrv\appcmd.exe set config "sitename.com/subfolder/bin/debug" -section:system.webServer/security/requestFiltering /-hiddenSegments.[segment='bin']

After making this change, you will be able to view pages normally, even if they have /bin in the site path.

The open source PHP dynamic language is one of the most widely deployed languages on Web servers today. But what operating systems are PHP developers using to develop and deploy their applications? It's a question that has been asked before and now it's being answered with a new study from Zend, one of the lead commercial backers behind PHP.

The study surveyed 2,000 PHP developers in December and found that 85 percent reported that Linux was their primary operating system as a production environment for PHP.

Windows came in at a distant second at 11 percent while Mac OS X came in third at just 2 percent. However, when Zend drilled down into which platforms respondents prefer for their development, the rankings change dramatically.

According to the study, 42 percent of respondents reported that Windows was their primary operating system for development. Linux came in as No. 2 at 38.5 percent while Mac OS X remained in third place at 19.1 percent.

The findings indicate that while Microsoft Windows remains the top platform for developing in PHP, its lead may be narrowing. Back in 2006, a Microsoft executive reported that 85 percent of PHP developers were developing on Windows, but only 20 percent deployed on a Windows machine. The change comes despite joint work by Zend and Microsoft to improve the capabilities of PHP on Windows servers.

that the new study was based on over 2,000 completed surveys conducted in December 2009, some of which came from Zend customers. The survey was made public through the Zend Framework website, the Zend monthly newsletter, Twitter and DevZone.

I have also noticed recently from reading blogs and lists that the majority of CFML open source developers seem to deploy Railo or Open BlueDragon on Linux, which is a major paradigm shift from ColdFusion developers who primary use Windows.

I don't think this is a matter of preference but rather one of necessity as pretty much all the PHP documentation is for Linux, most PHP apps are written for Linux/Apache and are not supported on windows even if you can get them working.

If you have tried to install Railo then will have discovered this can also be quite a task and a challenge to get working, especially on windows/IIS7, and there are far more blog posts and docs explaining how to get it running on Linux, as well as ready made virtual disk images, which I suspects encourages people to take the path of least resistance and install Linux.

In the case of CFML this does however tend to be done using virtualisation software such as virtualbox or vmware to run a linux development servers on windows, so cfml developers do still seem to be using windows as their primary desktop OS, so I do wonder if Zend took this into consideration with their study and if many of those who listed Linux as their primary development OS may in fact be running it as a virtual machine on windows. This feeling is further extrapolated by the fact that developers are mainly using servers distros like CentOS.

You also need to consider all the obvious facts as well:- While Linux has a lot going for it and plenty of software, most of the best/popular software, especially web dev/design products like Dreamweaver and the rest of the Adobe line is not available on Linux. Sure there are alternatives, but they are certainly not in the same league and you can't walk into PC World and buy any of it. For those who have always been running a Linux desktop this will of course not matter at all, but for the rest this will be a big issue, especially if it is software you have spent a lot of money on, so running a virtual machine makes sense.

Of course it could be the other way round entirely and developers are running a windows VM on linux, but this would seem an off way of doing it if their primary tools are on windows.

Before the Linux fanboys start ranting, let me make it 100% clear that this is not a linux vs windows slanging match and I will delete all churlish comments attempting to turn it into one. If you comment keep it on-topic and professional.

Been having a fun time today trying to get Magento CMS working. The bizarre situation was that PHP would work fine under the default web site, but not under any other web site, which would result in a 500 Internal Server Error caused by the ZendPHPviaFastCGI PHP handler mapping. See screenshot below. I of course tried every possible solution without success, the cause turned out to be rather obscure.

What was required to fix this was to manually add this attribute to the handler mapping in the applicationHost.config file, which you will find in C:\Windows\System32\inetsrv\config.

allowPathInfo="true"

This parameter does not seem to exist in the IIS Manager and is not even mentioned in the handler docs so I really do really not know why this is required or why it is not there by default and why you cannot add it via the GUI.

So the final entry for my ZendPHPviaFastCGI handler looked like this.

<add name="ZendPHPviaFastCGI" path="*.php" verb="*" modules="FastCgiModule" 
scriptProcessor="C:\Program Files (x86)\Zend\ZendServer\bin\php-cgi.exe" 
resourceType="Either" requireAccess="Script" allowPathInfo="true" />

Credit must go to my buddy Matt Gahan for working this one out.

PCI DSS compliance is now a legal requirement for anyone with merchant services, having just had to go through this myself and knowing that our clients are also going to have to do the same, I started searching for a simple guide that I could pass on to clients and came across this book.

Complying with the PCI Data Security Standard may seem like a daunting task for merchants. This book is a quick guide to understanding how to protect cardholder data and comply with the requirements of PCI - from surveying the standard's requirements to detailing steps for verifying compliance.

PCI Compliance for Dummies arms you with the facts, in plain English, and shows you how to achieve PCI Compliance.

And yes my company BlueThunder Internet is fully PCI DSS compliant before you ask :-)