Drupal 6.x

The Video module "transcodes" nearly any video format to H.246, Theora, VP8 (and many others) using either Zencoder cloud transcoding service or the open source FFMPEG project on your server. Site builders upload videos to nodes via a video field (which is part of the Video module) much like they would with the file field. When videos have finished transcoding, the Video module automatically creates thumbnails and will embed a video player into the theme layer.

References to Unix-like (*nix) commands in documentation or forum posts can be intimidating if you're not used to them, but sometimes "command line" is necessary for administering your system or fixing a problem.

Learning some of these *nix commands can help you be more productive, as well as give you insight into what your hosting control panel or GUI FTP client does.

CiviCRM requires a special installation process beyond copying it to your modules folder and activating it on the admin/modules page. For detailed instructions, consult the official CiviCRM documentation wiki:

To print the name of a node's content type, add these lines into your theme's node.tpl.php file.

Here's how to get mutltiple sites working on localhost using Windows XP. NB: This post was originally written for Drupal 4.6.x but has been updated for 6.x so some of the comments below are now obsolete.

Preparation

This page assumes that you have PHP, Apache, MySQL and Drupal all installed and working and have a MySQL admin tool available; the free community edition of SQLyog will do nicely, or you can use phpMyAdmin if you prefer. Again, I'll assume you've got one of these installed and connected to your database server. I'll use SQLyog here.

If you don't yet have PHP, Apache and MySQL installed then XAMPP will help! See also http://drupal.org/node/161975

Finally, I'll assume you're starting with a working D6.x installation, have followed the installation instructions and got the default site up and running. If not, start here http://drupal.org/getting-started/install.

If you attempt to load admin/build/modules and get a blank page, a message that says "The requested page could not be found" or a server error, this is most likely a memory issue.

When viewing this page, modules are (since Drupal 5.x) only loaded if they are enabled (previously, even disabled modules were loaded). Even so, a fair amount of ancillary processing takes place on this page and can cause PHP to run out of available memory. Note that all modules' .info files are loaded whether or not the modules are enabled.

There are two fixes:

1. Increase PHP's memory limit, e.g. to set it to 16MB try one of these:
   • memory_limit = 16M to your system's main php.ini file (recommended, if you have access. In case you don't, you can try to upload your own php.ini file in the root folder of your Drupal installation, but bear in mind that this will only have an effect if PHP is running as CGI)
   • ini_set('memory_limit', '16M'); in your sites/default/settings.php file (this doesn't work on all servers)
   • php_value memory_limit 16M in your .htaccess file in the Drupal root (this only works if PHP is running as an Apache module)