At last year's Drupalcon in Denver there was an excellent session called Delivering Drupal.  It had to do with the oftentimes painful process of deploying a website to web servers.

Recently, a user filed a dispute against one of my digital subscription-based websites.  Having never dealt with a PayPal dispute before, I went in not knowing what to expect.  I examined the user's account in Ubercart and they had definitely paid via PayPal and the IPN information was sent back to the site that the order had been successful.  The user had also received the digital subscriber role.  PayPal contacted me noting the user had filed a dispute against me that they did not receive the product.  However, I could see that they very clearly had.

ITWorld has a new article up about Joomla vs. Drupal and contains viewpoints of different developers.  I was asked by the author to give some insight on using either CMS so I'm in there around page two.  It's an interesting article because it's not from the perspective of one person and seems to cover many bases.

I noticed this happening while I was getting a site ready with the AddToAny Drupal module.  Pages would randomly hang in my dev environment and it was trying to contact Media6degrees.  After some Googling I found this was a third party tracking cookie being installed with the AddToAny module.  To disable it in Drupal 7, go to the modules page and click "Configure" next to AddToAny.  Under additional options near the bottom, paste this:

Here's a handy commandline snippet that will help you upgrade Drupal core (for example, 6.19 to 6.20) without having to replace everything.  It will only update the files that have changed.

Echodittolabs has a great and easy to understand write up about Drupal and web services.   If you ever need to interact with Drupal with an external application it looks like this is the best way to do it.

If you need a way to redirect webform submissions to a dynamic URL in Drupal 6, using the Webform PHP module can work well with Webform 3.x.  I recommend only using post processing conditionals on select fields if possible with Webform PHP since you need to enable the permission to "use PHP for additional processing" for users who submit webforms (typically anonymous).

Here's the process:

DrupalSN posted a nice guide to styling exposed View dropdown menus with a JQuery plugin and some stylish CSS.  The guide there worked perfectly except for the step where he hid the submit button.  I changed this:

.views-exposed-form label,
.jquery_dropdown_page .views-exposed-form .form-submit {
  display: none;
}

to this: