tips & tricks

Apr
29

Setting up WYSIWYG editor

WYSIWYG is an acronym for What You See Is What You Get, or a client-side editors (a.k.a. WYSIWYG editors) for editing content. Here is a simple step by step installation to get you up and running with WYSIWYG editor and make your end users happy. And if you owned a forDrupal themes, we have included goodies to use with WYSIWYG editor just for you.

This is part 2 of the setup, where we concentrate on making the server production ready. Part 1 focus on the basic server setup to get Drupal running, you can find Part 1 here.

Performance

Opcode cache helps speed up your PHP considerably. We are using APC here, there are other alternatives such as XCache, eAccelerator, Zend Optimizer, etc.

Install APC Opcode

This will install APC 3.0.18-1

# aptitude install php-apc

We've moved forDrupal to Linode VPS to serve you better. Since we just setup a server over there, we thought it would be nice to share it with you the process and served as a note for ourselves.

The following steps are conducted under Ubuntu 8.10 on a VPS. However it should be the same for newer version of Ubuntu or if you are setting up a dedicated server or a virtual machine.

Update: Linode just released Ubuntu 9.04 today, the steps here should be the same.

There are a number of useful Drupal modules quietly working hard at the backend on websites around the globe. They usually come without any visible UI to the end user. You should get to know about them. In alphabetically order:

  1. Backup and Migrate
    Simplifies the task of backing up and restoring your Drupal database or migrating data from one Drupal site to another, with automatic scheduled backups.
  2. Boost
Mar
10

block highlights

forDrupal's themes have a range of highlights styles to choose from to further enhance your content presentation. Highlights are highly suitable for custom block region.

Method 1

To use the highlights, you have to know basic HTML on applying classes to tags. A typical way is

<div class="highlight-blue"> … your content … </div>

You may need to change the input format depending on your configuration. "Full HTML" input format should always work.