Things have been and still are quite 'shop-ish' these days, meaning long hours in the shop working on some exciting sites. Therefore, apologies if this post is a bit 'shop-ish'. The discussion starts where Eric and I are talking about HelpEdit not showing up on path aliased pages in Drupal, which sparks some ideas...

Ok, couple of things were happening here. I’m going to document it well since it covers a couple aspects of drupal, and I want to further develop this module – i’m gonna say it—- it is the most useful yet least developed module in Drupal…and will only get more-so useful as Drupal continues to hit the masses, and the masses have to deal w/ working w/ drupal.

Helpedit was not designed to deal w/ path aliases set by the user, as far as I could tell. Also, I forgot to get rid of some permissions I inserted into the helpedit module. I thought I got rid of all of them, but I did not – I left one around the part that loads the help message on the page – a simple if (user_access(‘admin’)) { dothis }.

Many people thought they were just getting ripped off with their over priced software... turns out it is even worst. Convio is working with an anti-gay hate group, the Alliance for Marriage. What happens when the software vender that you pay to power your progressive online campaigns is taking your money to develop better tools to sell to your enemy? That is exactly what it appears Convio has been doing, as the Daily Kos reports.

Many people thought they were just getting ripped off with their over priced software... turns out it is even worst. Convio is working with an anti-gay hate group, the Alliance for Marriage. Find developers that care... buy open source.

Thanks Paul for the link.

So you are thinking about making the switch to an open source content management system because they are more robust and will be more powerful and cheaper to run in the future… how will you explain to your boss or board that the proprietary CMS you already paid $5,000 to $20,000 or more totally sucks?

This question came up three times in the last several months in conversations with prospective clients. Organizations bought licenses for proprietary CMSs and then realized they could have just downloaded an open source application for FREE that is better and more customizable, and in the end better meet their needs.

This option has actually become kind of a nightmare for some IT professionals because they see the cost savings of getting their site live faster and the long run benefits of using an OSS system that has a deep and active developers community.

Here are just two problems that surface again and again…

1) Staying on time: IT managers will no longer be stuck waiting for that promised upgrade/bug fix that was promised 3 months ago by the proprietary vendor.