I really hope this adds a ton of value to new or established businesses looking for more efficiencies in their web-contact-to-deal-close processes.

The plugin installs just like any other Wordpress plugin. It should be pretty intuitive to anyone that has even limited experience administrating a Wordpress site. The plugin can be downloaded from Wordpress or at my repo on github.

Fat Free CRM is a great customer relationship manager (CRM) I’ve been using for a little while now instead of Highrise. I used Highrise for a little while before I grew frustrated by its hosting costs and lack of features. The guys at 37signals don’t seem to update it very often either.

For the rails project, I forked the repository and made a few minor changes like adding access via an API key. I also added a few usability options in the view codes to make integration with the plugin seamless.

For new businesses that are just implementing a CRM solution, I’d be happy to host the CRM application on my servers for a nominal cost. Feel free to contact me for more details. (hint, the contact form is an example of the plugin in action )

To use the plugin and CRM together, just follow these simple instructions:

1. Download or clone the CRM from my github repo. Install on my servers (contact me for pricing) or on your own
2. Download and install the fat-free-crm-lead plugin either from Wordpress or my github repo
3. Configure the plugin with the URL of your CRM and an API token (details are provided in the admin interface of the plugin)
4. Watch the leads come rolling in and enjoy not having to copy and paste from emails any longer

Hopefully, this is really easy. If you run into any problems or have feature requests, please feel free to contact me.

====UPDATE====

The plugin has been accepted into the WP plugin directory. Take a look at the fat-free-crm-lead-form at Wordpress.

After hours of desperate searching, I finally found the solution to appropriate exception handling with php on IIS on the iis blog. The solution was more of a footnote about halfway down the page in the php.ini section. The trick is to set fastcgi logging to false. Not the most ideal solution, but I was finally able to handle exceptions the way php code should.

From iis blog: “FastCGI logging should be disabled on IIS. If it is left enabled, then any messages of any class are treated by FastCGI as error conditions which will cause IIS to generate an HTTP 500 exception.”

php.ini

fastcgi.logging = 0 ;

The music festival had just had a falling out with their core team of developers. They had an application with bugs and no support. Bryce was hired to become familiar with the code, do testing and bring the project up to production status.

This included re-factoring and building new code into the existing framework.

I also fixed their ailing e-commerce solution. The festival was unable to sell tickets to their events until I fixed that part of the code base

We developed a good relationship with the music festival by sharing frequent progress reports and handling new bugs quickly.