The code below goes in your template.php and removes the "More information about formatting options" link.

Please remember to clear the cache in order for the changes to trigger.

I recently had the requirement to hide a horizontal tab in node display depending on the value of a checkbox i.e. Show tab X. For the horizontal tabs I was using the excellent Fieldgroup module. In order to achieve the above, I created a little custom module and used the newly introduced in drupal 7 hook, hook_node_view_alter.

Here is some code to be used in a custom module in Drupal 7 in order to create a custom link in the admin menu.

Here is a handy, general function for Drupal 6 that takes as an argument a file id and returns the file for downloading. <?php function MYMODULE_send_file($fid) { $file = db_fetch_object(db_query("SELECT * FROM {files} WHERE fid = %d", $fid)); if ($file) { $my_path = $_SERVER['DOCUMENT_ROOT'] .'/'.$file->filepath; header("Pragma: public"); header("Expires: 0"); header('Cache-Control: no-store, no-cache, must-revalidate'); header('Cache-Control: pre-check=0, post-check=0, max-age=0', false); header('Last-Modified: '.gmdate('D, d M Y H:i:s') .?>

Here is the code that changes the default select list of "Select a product" element of Drupal Commerce to radio buttons, for a standalone product list. The following goes in a custom module (tested in Drupal 7).

In a custom module, I needed to get the latest node that each user published. It is fairly easy to goup by users, but it needs a little something to actually accomplish the sorting. The following query worked for me, we need to do the sorting in a nested select: In case the following error comes up:

Error: 1248 - SQLSTATE: 42000 ER_DERIVED_MUST_HAVE_ALIAS

One of my latests tasks was to allow a link that would take a user id and a node id as an argument, and automatically create a new order that would have some fields pre populated and ready for further editing. Scope is to use the user id as the client that does the order and to automatically select the product depending on the taxonomy term of the provided node. In my case I offer a series of links through a custom view template, that uses data from each row results to built the link. Here is the code for my module, hopefully it will be useful for someone:

In some cases it is seems impossible to get rid of the duplicate entries that views return in the output. Not an elegant way, but this small module would do the trick... So let's create a module the usual way, and put the following code in the .module file. This one is called remove_duplicates. _views_pre_render(&$view) { $used_nids = array(); foreach ($view->result as $row) { if (!in_array($row->nid, $used_nids)) { $new_view_result[] = $row; $used_nids[] = $row->nid; } ?>

There are so many reasons to use Content Profile instead of the user's core profile. For once, profiles are created as separate nodes and therefore the full flexibility of CCK and VIews come in the game. This way it is possible to build some really sophisticated profiles, which is usually what is needed for any website. I had to look around for an easy solution on how to load the user's content profile programmatically, so the following might come in helpful.

Here you can find some simple tests that would confirm the smooth functionality of your crontab.

Test if cron is running

Type the following command:

ps ax | grep cron 

Make sure that cron shows up. Expected output should be something like

[konordo@konordoserv]# ps ax | grep cron
 1185 pts/1    S+     0:00 grep cron
 1771 ?        Ss     0:00 crond
 

Test if cron is working

Add the following entry to your crontab. To do so, enter the command

crontab -e