Hosting for just $3.88/month! Find out MORE!

Archive for the 'wordpress' Category

Page 3 of 5

Running multiple WordPress domains

After migrating a few of my blogs to a shared server, I’m seriously looking at how to run multiple WordPress blogs with the same code.

Here are my requirements

  1. Use 1 instant of WordPress code.
    When a new version is released, I just have to update this one instant.
  2. The resulting blogs appears on different domains.
    For example, example.com, 59ideas.com, seekingrevenue.com
  3. The files are on the same server but not necessary the same Apache server root
    Many hosting use domain pointers so that multiple domains are hosted like this:
    /somepath/www/example
    /somepath/www/59ideas
    /somepath/www/seekingrevenueor it should work like this too:
    /somepath/example/www/
    /somepath/59ideas/www/
    /somepath/seekingrevenue/www/
  4. Since each blog is standalone, it should have
    • separate theme
    • separate plugins
    • separate upload files
    • separate .htaccess, permalink structure

I decided against Wordpress Mu because there might be a (remote) chance that the site will move into different servers again. When that happens I want to just install a copy of plain old WordPress.

Looking around, these look like promising approaches.

  1. echo “Hello Again, World!”; by Stephen Rider
  2. Multi-blogging for Wordpress update by Bruce Kroeze

AdAdvantage K2 scheme updated to R5

It has been a long time since the last update of AdAdvantage. In the meantime, WordPress has gone from 2.0.x to 2.1.x to 2.2.x.

Since K2 stopped supporting WordPress 2.0.x, it means that I need to first upgrade my 2.0 blogs before updating K2, thus ensuring a long procrastination.

This release is not just an update but a throws in a few improvements as well.

  1. First and most significant (to me at least), files and code are now hosting on Google Code. So just head over and grab the latest copy release file.
    Interim update will be posted to the subversion repository, so no more waiting for the final release.
  2. CSS clean up.
    The theme no longer use the older 3 column code but tries to maintain as close to the original K2 code as possible. (you can use WinMerge to compare).
    Some adjustments to the original css are added to the scheme css so that original css is untouched.
    Improvement and suggestion are most welcome, please leave a comment.
  3. Dropped custom sidebar codes and blocks to use sidebar widgets instead.
    No reason to continue hacking the sidebar when the widget is so much easier.
  4. Added some dummy ad formats for placement in different locations.
    Please suggest other location and placement methods. This is one area that I would like to improve on for this scheme.

To download file., just go to the project page on Google Code.

Enjoy!

WordPress updated, AGAIN

WordPress announced that 2.1.3 and 2.0.10 had been released. Update had been so frequent that keeping up is becoming a fulltime job for a blogger.

Do you keep up to date with every release?

Just thinking, wo you think you would be interested in an upgrade service that charges you say $5-$10 an upgrade or say $30 for 1 year of any update released?

Upgrading WordPress to 2.1.2

After procrastinating for a short while, I decided to slowly upgrade all my WordPress 2.0 blogs to the 2.1 series.

Although there are problems, gotchas and even downgrade reported, it really isn’t so frightening.

On the WordPress site there are some excellent documentation on upgrading. Be sure to read them first.

After reading them, I had worked out a few steps that is differ from the instruction which I’m sharing here. (Be sure you understand what you are doing if you want to try following them.)

If you have a few blogs, try it out first on the less trafficed blog.

I decided not to Delete the old WordPress files. Over time I had added many files and folders to my WordPress folder. Isolating what to delete and what to keep is too time consuming. Instead I just overwrite with all the files from the 2.1.2 download.

Note that this will not work if you had make changes directly to WordPress files. In most case, stay clear of editing core files.

Next I do a compare with unix diff command. If you are on a Windows platform you might want to try WinMerge.

diff -rq wordpress/ www/

There isn’t too much difference so I copy out all the differences and make it into a list of command.

cd wp-includes
rm wp-l10n.php
rm template-functions-post.php
rm template-functions-links.php
rm template-functions-general.php
rm template-functions-category.php
rm template-functions-author.php
rm pluggable-functions.php
rm links.php
rm functions-post.php
rm functions-formatting.php
rm functions-compat.php
rm feed-functions.php
comment-functions.php
rm js/dbx-key.js
rm js/tinymce/plugins/autosave/langs/cs.js
rm js/tinymce/plugins/autosave/langs/sv.js
rm js/tinymce/plugins/inlinepopups/editor_plugin_src.js
rm js/tinymce/plugins/inlinepopups/readme.txt
rm js/tinymce/themes/advanced/editor_template_src.js
cd ../wp-admin
rm edit-form-ajax-cat.php
rm execute-pings.php
rm inline-uploading.php
rm link-categories.php
rm list-manipulation.js
rm list-manipulation.php

Basically everything should be working up to this point. Click around and see if everything is working.

Next is to activate the plugins. Depending what plugins and the number of plugins you used, this can be a more problematic and time consuming part of the upgrade. I will follow up with another post on this.

Test out the site for a few days before moving on to your next blog.

Oh, and of course I’m going to update the AdAdvantage K2 scheme to work with 2.1.

Now my comments are spam

At least Akimet thinks so.

Lately I noticed that my own comments reply are not appearing. I was pretty sure the comments were posted. After some test, it turned out that Akimet marked them as spam! It some became a pain to have to go into the admin after every reply to unspam my own comment.

One problem of living and accessing the Internet from China is that many spam filter consider my IP as a spam source. I had similar problem before commenting on Jeremy Zawodny’s blog.

Akismet do not reveal how spam are determined so it is not clear if Akismet use IP as one of the factor. I would hate to think that it was my email or URL and certainly the content of my comments does not read like spam.

After digging around it seem like there is an option in Options > Discussion, right at the bottom, there is a checkbox,

Blacklist comments from open and insecure proxies.

Backlist! Don’t get me started on why blacklist is a bad idea.

No luck after unchecking the option. My hope now is the false-positive feedback to Akismet really work.

[tag]spam, akismet[/tag]



59ideas Sites

Pro Themes

  • Affiliate Theme
  • Premium WordPress Themes