Back to top

Technology

Broadly defined "technology" e.g. software, water pumps

remove "not verified" from comments

Note: this is a really bad way to do this - see the comments for the right way.

I disagree on this point, but a friend asked and other folks have previously been confused so I removed the "not verified" label from a site and I was confused on where to do it. A little bit of grepping and I found it's in common.inc:

@@ -898,7 +899,8 @@
$output = $object->name;
}

People Involved: 

Remove Table of Contents from Drupal Book

Continuing on from the project I just mentioned...I wanted to remove the list of pages (which is analogous to a table of contents) from the book pages. On this particular site I'm using the book block on the right hand side, so having this information on the bottom of top level page makes for duplication of links and just seems plain funny. Below is the relevant diff -u on the subject:

People Involved: 

Dates in Drupal

So, I'm converting a site from a current static HTML version to a drupalized version and in the process we are taking comments that were created over email from a "contact me mailto:" email on the old site and putting them into forum discussions on the new site. Most of the discussions were "receive email, send response" variety, so it's just a node and a comment.

In order to give a feel of the time of the original email and the response, we used the node administration facility of setting the time when creating the nodes. That works great, but when you enter comments you don't have the same control over the time. So, we calculated the average response time in the emails and decided to set comments to be that far in the future after their node. The first curious thing to me was figuring out what dates in Drupal are based on - turns out it's the Unix Timestamp which is fairly common.

So, armed with the knowledge that the average comment lag was 183807 seconds, I ran the following sets of queries to get the desired offset:

mysql> create table gjk_junk as SELECT n.nid, created +183600 as new_time FROM node n inner join comments c on n.nid = c.nid;
Query OK, 19 rows affected (0.96 sec)
Records: 19 Duplicates: 0 Warnings: 0

mysql> create table comment_bak as select * from comments;
Query OK, 19 rows affected (1.61 sec)
Records: 19 Duplicates: 0 Warnings: 0

mysql> update comments c, gjk_junk g set timestamp = new_time where c.nid = g.nid;
Query OK, 19 rows affected (0.20 sec)
Rows matched: 19 Changed: 19 Warnings: 0

mysql> select c.cid, c.timestamp, b.cid, b.timestamp from comments c inner join comment_bak b on c.cid = b.cid;
+-----+------------+-----+------------+
| cid | timestamp | cid | timestamp |
+-----+------------+-----+------------+
| 2 | 1140696532 | 2 | 1141291314 |
| 3 | 1110370045 | 3 | 1141291509 |

People Involved: 

Penny for your Email

Spam is a problem, right? Everybody hates it except for the people making money on it.

Penny Email

Currently, spam is a cost to the service providers (it uses large amounts of network and disk space - fortunately, both of those are fairly cheap) and it's a problem for people who don't have unlimited time in their lives.

A while ago I subscribed to Computer Power User and read an article by Rob Malda (cmdrTaco to you /. folks) about charging a penny per email.

People Involved: 

Predictive Markets - Can't Wait Until 2008

Predictive Markets

Predictive Markets are a really neat idea. Basically, you let knowledgable people bet on the likelihood of a particular event happening: Bush getting re-elected, 10 inches of snow falling in one day on New York City by 2008, or Nikki letting me buy a new computer this year. Then the price of the contract for that particular event will then reflect the collective knowledge of the community about that event. If you have something that is hard to analzye or hard to predict, this is a great way to get a fairly reliable answer.

Greed is good

People Involved: 

Pages

Subscribe to RSS - Technology