Problem:

Stylesheets are always returning https since 2.7 as shown in the source code:

<link rel="stylesheet" href="https://www.vincentkong.com/wp-content/themes/glossyblue-1-4/style.css" type="text/css" media="all" />

Cause:

The cause of the problem is due to the following code found in the  wp-includes/link-template.php.  More specifically with the line if ( is_ssl() ) since it seems to always return true if you have SSL enabled for the website.

/**
 * Retrieve the url to the content directory.
 *
 * @package WordPress
 * @since 2.6.0
 *
 * @param string $path Optional. Path relative to the content url.
 * @return string Content url link with optional path appended.
*/
function content_url($path = '') {
 $scheme = ( is_ssl() ? 'https' : 'http' );
 $url = WP_CONTENT_URL;
 if ( 0 === strpos($url, 'http') ) {
 if ( is_ssl() )
 $url = str_replace( 'http://', "{$scheme}://", $url );
 }

 if ( !empty($path) && is_string($path) && strpos($path, '..') === false )
 $url .= '/' . ltrim($path, '/');

 return apply_filters('content_url', $url, $path);
}

Solution:

As a quick solution I commented the portion of code which was causing the issue.  I don’t know what is the side effect of this, but I haven’t ran into any issues yet.

 if ( 0 === strpos($url, 'http') ) {
 if ( is_ssl() )
 $url = str_replace( 'http://', "{$scheme}://", $url );
 }

Update:

As of version 2.8.5 a new JavaScript in WordPress is also always referencing https

<script type=’text/javascript’ src=’https://www.vincentkong.com/wp-includes/js/jquery/jquery.js?ver=1.3.2′></script>

To resolve this open wp-includes/script-loader.php and comment out the line indicated below:

function wp_default_scripts( &$scripts ) {

        //if ( !$guessurl = site_url() )
                $guessurl = wp_guess_url();

As of version 3.0 another custom change needed to be made to fix the https referencing.

Open wp-includes/functions.phpand comment out the line:

function wp_guess_url() {
...
//$schema = is_ssl() ? 'https://' : 'http://';

Related posts:

1. WordPress Plugins
2. WordPress Quickstart Guide
3. Permalinks in WordPress

By default WordPress comes with the Akismet plugin which checks your comments against the Akismet web service to see if they look like spam or not. However, to activate this plugin you need a WordPress API key which can be obtained by registering to WordPress.com.

Not wanting to register with WordPress.com, I went to see what the WordPress community had to offer. I decided to use Wp-SpamFree, which was one of the more popular and higher rated plugin. The plugin blocks spam without using CAPTCHA or challenge questions, and once activated the plugin will display the number of blocked spams on the dashboard.

Other plugins which I use are mention in my previous blog: WordPress Plugins.

Related posts:

1. WordPress Plugins
2. Migrating to WordPress 2.5.1
3. Permalinks in WordPress

WordPress offers you the ability to create custom URL structure for your permalinks and archives, which improves the readability, and forward-compatibility of your links e.g. http://example.com/category/post-name or http://example.com/year/month/day/post-name. To enable permalinks you first need to enable mod_rewrite for Apache. In Ubuntu execute the following:

$ sudo a2enmod rewrite

In the Apache configuration file, the FollowSymLinks option needs to be enabled and the FileInfo needs to be allowed for the WordPress’s home directory.

<Directory /var/www/wordpress>
    Options FollowSymLinks
    AllowOverride FileInfo
    allow from all
</Directory>

Create a .htaccess file inside the WordPress’s home directory and set read/write permission to it.

$ cd /var/www/wordpress
$ touch .htaccess
$ chmod 666 .htaccess

In the WordPress Dashboard navigate to “Settings” > “Permalinks”

Specific the URL structure which you desire, and click on the “Save Changes” button.

For security purposes remove the write permisson on the .htaccess file

$ chmod 644 .htaccess

Related posts:

1. Migrating to WordPress 2.5.1
2. WordPress Quickstart Guide
3. Gallery2 URL Rewrite Plugin

To install a typical plugin, download the plugin and extract it into the wp-content/plugins folder of the WordPress root folder. In the Dashboard, click on the “Plugins” link and the “Activate” link to activate your plugin.

Plugins which I installed

Broken Link Checker: This plugin is will monitor your blog looking for broken links and let you know if any are found.

This requires the CURL library to be installed for PHP, otherwise an error will occur: Fatal error: Call to undefined function curl_init().

To install CURL library for Ubuntu:
$ sudo apt-get install php5-curl

Link Summarizer: This plugin produces a list of all the links you referred to in a posting. You can exclude links from the summary by specifying regular expressions for links that shouldn’t show up. For example, the regular expression I used to ignore links to the images of my blogs:

^http:\/\/.*\.vincentkong\.com\/.*\.(gif|png|jpg)$

Wordbook: This plugin allows you to cross-post your blogs to your Facebook Mini-Feed. Your Facebook profile will also show your most recent blog posts. This works similar to importing your blog’s RSS feed with Facebook Notes, but with some advantages as described in the Wordbook FAQ.

WP-ShortStat: WP-ShortStat is a litte statistics plugin for WordPress.

WP-Table: This plugin creates and manages tables for WordPress.

Related posts:

1. Stopping Spam in WordPress
2. Migrating to WordPress 2.5.1
3. Permalinks in WordPress

Installing WordPress

Download and the latest release of WordPress.

$ wget http://wordpress.org/latest.tar.gz

Extracting the file will create a new directory wordpress, move all the files into the a web server’s public HTML directory.

$ tar -zxvf latest.tar.gz
$ mv wordpress/* /var/www/wordpress

Create a MySQL database and user for WordPress

mysql> CREATE DATABASE databasename;
mysql> GRANT ALL PRIVILEGES ON databasename.* TO 'username'@'localhost' IDENTIFIED BY 'password';

Create a wp-config.php file and modify it to specific your WordPress settings.

$ cp wp-config-sample.php wp-config.php
$ nano wp-config.php

define('DB_NAME', 'putyourdbnamehere');
define('DB_USER', 'usernamehere');
define('DB_PASSWORD', 'yourpasswordhere');
define('DB_HOST', 'localhost');

The database character set, normally should not be changed.
define('DB_CHARSET', 'utf8');

The database collation should normally be left blank.
define('DB_COLLATE', '');

In version 2.5 WordPress introduced a new optional entry called SECRET_KEY, which enables better encryption of information stored in the user’s cookies.

define('SECRET_KEY', 'put your unique phrase here');

It’s recommend to change the value of the SECRET_KEY to a unique phrase. To help generate a unique phrase visit the WordPress secret key generation site. For more information on the SECRET_KEY refer to the Editing wp-config.php page.

Run the install script by pointing your browser to the URL of your website (e.g http://www.vincentkong.com).

After the installation has been successful, it’s recommend that you immediately login and change the randomly generated password.

Related posts:

1. MySQL for Ubuntu Quickstart Guide
2. Drupal Quickstart Guide
3. Gallery2 Quickstart Guide

Related posts:

1. Migrating to WordPress 2.5.1
2. Stopping Spam in WordPress
3. WordPress Plugins

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.

Related posts:

1. Finish Migrating to WordPress
2. WordPress Plugins
3. Stopping Spam in WordPress

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

Related posts:

1. Configuring Multiple Sites with Drupal
2. Drupal Quickstart Guide
3. Installing TinyMCE Editor in Drupal

Before you start download the following:

• TinyMCE module
• TinyMCE Editor itself maintained by Moxiecode Systems AB

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

Related posts:

1. My Profile Settings for TinyMCE Editor
2. Configuring Multiple Sites with Drupal
3. Drupal Quickstart Guide

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>


Related posts:

1. Drupal Quickstart Guide
2. Installing TinyMCE Editor in Drupal
3. Configuring Cron Job for Drupal