Blog

I first noticed this issue when using Drush to enable a module. Drupal core will present a warning displaying something along the lines of:

orphaned actions (comment_publish) exist in the actions table. Remove orphaned actions

The answer wasn't readily Googled, but after some quick digging I found 2 solutions.

Method 1

Login as user 1 aka 'admin' and visit: http://yourwebsite.com/admin/settings/actions/orphan.

This is a quick snippet of how to effectively count the number of rows within a table. There are actually two approaches to take, depending on the markup of the table.

Using a HTML4 style table

$('#tableID tr').length;

Using a XHTML style table

$('#tableID >tbody >tr').length;

When testing this, you can place this code in an alert() or a console.debug() if your using Firebug.

This post is imported from my old blog

The other day at work, I thought I would see how steam run on my work computer. Well, my ports were all blocked by the network except the normal 80, 22, 21 etc. I then thought maybe I could simply tunnel my traffic through my SSH connection

Before we get anywhere, you NEED access to some kind of SSH. I have DD-WRT running on my home router which gives you the ability to login via SSH, I won’t get into that. You can google how to setup an SSH session. Also you will need admin access on the machine your trying to run steam on.

As a starting point for my new blog, I'll walk you step by step on how to export your views to code. Before we begin though, I bet your first question is:

Why?

Views are stored in the database and therefore can not be put into revision control. Like much of the Drupal system, the meat-and-potatoes of your website are stored in the database, and Views are no exception. If you should ever need to make a change to a view, you have nothing to roll back to, at least not without restoring a database backup, which is just silly.