webtech
Drupal and Feedburner
Submitted by Christian Nally on Fri, 2007-02-09 22:15.
[ this post is now obsolete given the new Feedburner Drupal Module ]
I've started using Feedburner to track 'subscriptions' to my site. It's clear that the simplest way to reach out to folks is through the e-mail newsletter, but some fraction of the audience will be using feeds, and so I might as well set myself up to track that.
There is an excellent page here regarding how to best use Drupal and Feedburner together. Here's my executive summary for all you executives.
- Set up a URL Alias (admin/path) for feedburner to be pointed at. e.g. example.com/fbfeed if your drupal site was on example.com [ we -won't- have the server redirect this URL ]
- tweak your .htaccess file to include the following:
Redirect temp http://example.com/rss.xml http://feeds.feedburner.com/YourHost
Redirect temp http://example.com/node/feed http://feeds.feedburner.com/YourHost
Power users should definitely read through the reference for this method.
Sticky
Submitted by Christian Nally on Mon, 2006-10-09 23:53.
Today's entry is getting put in place so I can stop the vicious cycle of going back to the man pages every 6 months to figure this out, again.
***
You know how sometimes you'd prefer to have the files you create show up with a specific group? Welcome to the sticky bit. It's all about directories.
If you make a new file in a directory, what group will it have? Your default group? Not if the stick bit is set. In that case, the group of the new file is set to the group of the directory it's appearing in.
Let's say you've just set up your directory to have the proper group and you'd like it to stay that way. Here's a command that will go down through the file heirarchy and set the sticky bit on all the directories.
Windows Add Hardware Wizard
Submitted by Christian Nally on Thu, 2006-10-05 03:39.
Just because the following posting just saved my digital bacon I'm going to give it a link/vote of confidence in hopes that others in need will find it.
I had the following error message, and Windows clearly had the situation wrong.
