After changing some settings, adding some plugins, tweaking the theme, and reorganizing the content. I have finally finish the migration to WordPress. However to not forget how my previous website looks like I have taken a screen shot.
After using Drupal for about a year, I’ve decided to migrate my site to WordPress. Drupal worked for me, but I thought it was a bit more complex to use for hosting a simple blogging site like mine. As well, the the organization of it’s modules and themes are lacking and confusing to use. This is where WordPress impressed me, it’s very lightweight, as it consist of half the table structures when compared to Drupal. There are many plugins, and themes available for downloading.
There are still some stuff for me to clean up, but I have migrated all the content from the old site already. Later, I’ll post up information on how to setup WordPress and it get working.
Some modules require regularly scheduled actions, such as cleaning up log files. You can make these happen automatically by using cron jobs. Schedule a cron job that regularly visits the “cron page”. This regular visit will automatically tell Drupal to perform its periodic tasks, and this will help keep your system running smoothly.
If your site is http://www.example.com then the page would be found at http://www.example.com/cron.php. Here is an example of a cron job that uses wget to visit the cron page:
0 2 * * * wget --quiet http://www.example.com/cron.php
TinyMCE is a platform independent web based Javascript HTML WYSIWYG editor.
Before you start download the following:
Extract the TinyMCE module into the the directory below. This is where the integration code is located.
sites/all/modules/tinymce
Extract the TinyMCE editor into the directory below. This is where the actually editor is located.
sites/all/modules/tinymce/tinymce
Enable the module by navigating to:
Administer > Site building > Modules
Setup the permission to determine who can use this module by navigating to:
Administer > User Management > Access Control
To configure TinyMCE, a new profile needs to be created by navigating to:
Administer > Site Configuration > TinyMCE
If you use Filtered HTML for your Input format, then you may need to modify the Allowed HTML tags list depending on what buttons you chose for your profile. For example, bold, italic, and underline button will need the <b>, <i>, and <u> tag added. To change the Input formats navigate to:
Administer > Site Configuration > Input formats
A single Drupal installation can host several Drupal-powered sites, each with its own individual configuration.
Configuration
Additional sites configurations are represented by creating subdirectories under the ‘sites’ directory of the Drupal installation. For example, the configuration for www.vincentkong.com could be ‘sites/www.vincentkong.com’. If users can access the site at http://vincentkong.com as well then ‘www.’ should be omitted. Subdomains are also support, for example, my.vincentkong.com would be ‘sites/my.vincentkong.com’. Drupal will transverse through the directories and find the best matching directory for the site requested.
After the proper directory for your domain has been created copy the default configuration file ‘/sites/default/settings.php’ into the your new directory.
$ cp ./sites/default/settings.php ./sites/vincentkong.com
Run the install script by pointing your browser to the base url of your website (e.g http://www.vincentkong.com), and follow through with the setup screens. Ensure that you DO NOT overwrite any existing databases.
Site-Specific Modules and Themes
Each site can have it’s own specific modules and themes in additional to those installed in the standard ‘modules’ and ‘themes’ directories in the base installation. To use site-specific modules or themes, create the ‘modules’ or ‘themes’ directory within the site configuration directory.
$ mkdir ./site/vincentkong.com/modules
$ mkdir ./site/vincentkong.com/themes
Apache
When setting up virtual hosting for Apache to support multiple sites for Drupal, the DocumentRoot for all the sites should be set to the base directory of the Drupal installation. For example if my Drupal was installed in /var/www/html
<VirtualHost *>
ServerName www.vincentkong.com
DocumentRoot /var/www/drupal
</VirtualHost>
<VirtualHost *>
ServerName my.vincentkong.com
DocumentRoot /var/www/drupal
</VirtualHost>