Mike Harris's blog

A group that I've been involved in has produced a new web site called Tech Tools for Activism to go alongside a booklet that we produced some time ago.  Tech Tools for Activism, or TTFA for short, aims to provide a portal (to use the old .com term) for social and community activists and grassroots compaigners to find out information about the alternatives to corporate IC

There's lots of web sites that provide link shorteners (bit.ly, tinyurl.com, imc.li, tiny.booki.cc; to name but a few).  In the past I'd always used tinyurl.com, but then I started working on a project to provide a book of useful technical tips for political activists and grassroots campaigners and some people on the project were concerned about the security implications of third parties logging the redirects, having to have a named account in order to edit the links and the potential of the lin

I was getting the message An illegal choice has been detected. Please contact the site administrator. when submitting forms, and more annoyingly when doing an AJAX image upload on a form.

The problem is caused by the radio buttons that I have on my form.  They are set up without a default value but as required.  I believe the issue is that if a radio group dosen't have a value set, it doesn't existing within the DOM for the form in question, therefore leading to an error on the form checking.

Some users on a Drupal site I have can create nodes which aren't published immediately; they need to go through a moderation process by the site admins.  The content type in question is set not to publish right away.  When I added a new node as a user all I got was the standard Drupal 'Content type Not another story again! has been created.' in a green box:

I was pulling my hair out about some Drupal 7 Views weirdness!  For some reason my normal users weren't able to view their own unpublished content even though they had the permission View own unpublished content permission set under the Node section.  Users could view and edit the node if they went to the node directly, but it wasn't possible to show the node in a view, unless the user was an Administrator that is.  I had got to the point of installing and using the Views Unpublished module, but this seemed like an imperfect solution.