Category : tools

Help Test RSS Digest 1.1 Beta

I’m close to being able to push out an update to RSS Digest, version 1.1, but I would like to hear from some beta testers before pushing it out to the world. If you use RSS Digest and are comfortable on the bleeding edge, I’d appreciate it if you tested the beta.

The main features are in the reliability and debugging department. In particular, I’ve made enhancements to the scheduling algorithm and have included several new debugging tools.

Sorry, if RSS Digest is working great for you, this release won’t offer much in terms of shiny new features. Rather, my goal for this version is to make it easier to help the occasional user who runs into trouble.

Here are the instructions for installing the beta version of the plugin. (Of course it is always a good idea to make a database backup before upgrading WP or any plugins!)

1. Deactivate the current plugin in WordPress Settings
2. Delete the existing rss-digest directory under wp-content/plugins, or move it if you’ve made changes, e.g. to css
3. Download the beta version of the plugin to your wp-content/plugins directory:

http://downloads.wordpress.org/plugin/rss-digest.1.1-beta_3.zip

4. Reactivate the plugin in WordPress

To check out the new debugging tools, go to the new Debug tab in the Settings > RSS Digest page. Check the “Turn on detailed logging” button. Enter your feed, schedule and option information on the main Settings tab. View the log after the scheduled time to see what happened.

Thanks for helping and please use the comments below to keep me posted! I’d like to hear from you whether all goes well or you run into trouble.

Django-uploadify-s3 sample application now available

A couple of weeks ago I wrote about django-uploadify-s3 (DUS3), a Django application that makes it very easy to add browser-based uploads to your Django projects.

If you are interested in DUS3, you will probably also be interested in django-uploadify-s3-example, a well-commented sample project that incorporates DUS3 for HTTP POST uploads to Amazon S3. Please check it out and let me know what you think. Like django-uploadify-s3 itself, django-uploadify-s3-example is posted up on github.

Link: https://github.com/sbc/django-uploadify-s3-example.

A couple of cool Mercurial plugins

Last month I posted on git vs mercurial, concluding based on first impressions and hearsay that I’d probably like Mercurial. So far so good. I’ve been using Hg pretty regularly for a project and while I haven’t really needed to do anything fancy I can say that so far it has been very intuitive to use.

Along the way I’ve found a few interesting resources that I’d like to share:

The Hg-Git Mercurial plugin. This plugin, hosted by the folks at github, allows seamless access to git repositories from Mercurial. It works as advertised, though when I first installed it I received HTTP 406 errors when trying to clone a git repo. Turns out I had copied the HTTP URL instead of the git URL. Get that right and everything seems to work great.

The Hgkeychain Mercurial plugin. This plugin allows Hg to store passwords for remote repositories in the Mac OS X keychain. (I sought this out pretty quickly as I got tired of logging into bitbucket.)

Hg Init: a Mercurial tutorial. I haven’t actually read this yet, but this six-part tutorial by Joel Spolsky of joelonsoftware fame looks really good.

Let me know if you’ve got any other must-have Mercurial tools or resources.

All you really need to know about Git vs. Mercurial

I recently came across a note on the Atlassian acquisition of Bitbucket, a code hosting site much like github. In a blurb about the service, one thing in particular caught my eye — they offer a free account with unlimited private repositories. I’ve dabbled with Git, and like it, and think Github is very cool, but I’ve always been put off by the need to pay for a private repository. Instead, I’ve set up a repository in my dreamhost account and that works great, but I’d prefer the convenience and polish of a commercial hosted service. My quick review of the Bitbucket site was promising, but … Bitbucket works with the Mercurial DVCS.

While I like Git, I’m far from wed to it, so I started to look into Mercurial (aka Hg). It turns out everything you need to know about Git vs. Mercurial can be summed up in a catchy analogy: Git is McGyver, while Mercurial is James Bond. This is the argument advanced by Patrick Thomson in very articulate blog post “Git vs. Mercurial: Please Relax.”

If you are wondering about Git vs Hg you should definitely read Patrick’s post, but here are my takeaways:

  • Git is more flexible and will have some advantages if you are working on a large team or want to build other applications on top of it
  • Mercurial is more user friendly and will be easier to deal with if you’re working on small projects
  • Mercurial has taken steps to ease the transition for SVN users, while Git can at best be said to ignore this issue

Patrick’s description of working with Git resonated with my own experience. While my ‘happy path’ experience with git was always good, on several occasions I ended up with the repository in a state that made it clear that I would need a pretty deep understanding of how this thing worked to seriously depend on it. I found, but balked at digging into, Git Internals, an apparent rite-of-passage to truly grokking the tool.

While I’ve not yet even downloaded Mercurial, Patrick’s description of that tool resonates strongly as well, if only in contrast to git. I think I’ll like it. I’ll let you know.

If the McGyver vs James Bond analogy doesn’t work for you, you can try this lighter post, which compares the two tools to Wesley Snipes and Denzel Washington.

Remote browser screen shots, i.e. how to make sure your site doesn’t look like crap in that other browser!

This morning robyn, a Geek Factor visitor to whom I’m eternally grateful, used the site’s contact form to let me know that my site looks like crap on their computer. It said it with a bit more diplomacy, of course, but that was the general idea.

hi, was looking forward to reading your information, but your website template is really screwed up, everything is about a 2pt. font. i was struggling to read it. your template is narrow and your pictures is full size.

just wanted to let you know

I know the site looks fine in Firefox, my everyday browser of choice, so I guessed that robyn was an IE user. My first step was to see how bad things were. Problem is, I’m on a Mac. (Ok, I could have launched a VM but that’s a PITA that I’d rather avoid.)

Years ago when I’ve had to do this kind of thing I used BrowserCam, a subscription-based web app, that takes screenshots of your site in different browsers and operating system combinations. A quick Google search turned up the fact that there are now a number of new, and FREE, options, including BrowserShots and Adobe BrowserLab. Awesome!

Adobe BrowserLab

The first of these that I tried was BrowserLab. You need an Adobe ID to use it, but beyond that it’s free, at least for now. As you might expect from Adobe, BrowserLab is a nicely designed Flash application. It gets the job done well and has some nice features like a zoom feature and the ability to do side-by-side comparisons of your page in different browsers. I didn’t need either of these, because the site was clearly FUBARed in IE. BrowserLab worked well for my needs and I recommend it.

BrowserShots

Just for kicks — really for this post — I also tried out BrowserShots. BrowserShots is an ad-supported application and, as a result, the user interface is a bit of a mess. That said, it has some distinct advantages to BrowserLab, the most important being the fact that no account is required to use it — if you just need to run a quick test and don’t already have an Adobe ID, BrowserShots is the place to go. In addition, BrowserShots supports an insane number  of browsers, many of which I’ve never heard of. (Dillo, Epiphany, Kazehakase anyone?) Like BrowserLab, BrowserShots gets the job done.

Conclusion

We’ve come a long way in two or three years and there are a number of free and functional options available for making sure that your site looks good across platforms. I have no idea how long Geek Factor has been looking stinky in IE — I can only assume it’s been quite some time — but BrowserLab helped me find and fix the problem quickly.

Geek Note: The problem was that a font size of 62% was applied both in the base CSS of the site’s theme framework, Thesis, as well as in my custom CSS.