how-to

Blog Herald: Wordpress 2.5 Upgrade Checklist

"I recently asked if you were ready for WordPress 2.5, but let’s go through the steps to prepare your blog for upgrading to the new version next week."

Complete Story found via Weblog Tools Collection

Kevin Millecam: Douglas Search Tips for Drupal

Kevin Millecam writes a great summary of helpful tips for utilizing search in the Drupal CMS. Most of the tips provided originated from Robert Douglas.

Complete Story

CIO: How to Build Your Own Wikipedia

Wikis are useful business tools. With planning and some staff time, you can make your own online collection of useful articles, tailored to your organization's needs, to communicate about business processes, manage collective know-how and more.

Complete Story

OSC: The Art of Joomla!

"So, it is no small matter to learn that Andrew [Eddie] recently launched The Art of Joomla!.
Teaching is something Andrew is very good at, and in this monthly
webazine, we will learn from the Master about the inside and outside of
a Joomla! v 1.5 website.

The Art of Joomla!: Issue 1 is entitled Opening the doors to the developers' and designers' revolution. There is an Editorial, Security Essentials section where this month Stumping the Spoofers where Cross Site Request Forgeries is discussed."

Complete Story


Charlie Gordon: How to: create a wiki with Drupal

"Over
the past two years, Drupal's wiki capabilities have expanded
exponentially. Yet, still we get support requests on the forums, "How
can I make a wiki with Drupal?" Well, here is a detailed plan that
gives wiki functionality to Drupal. This tutorial assumes you're
starting with an installed version of Drupal 5.x, and that you're
familiar with installing modules."

Complete Story

Optimizing Xoops, its modules and your server

Recently posted at XOOPS.org was a how-to for optimizing XOOPS on your server.

Optimizing Xoops, its modules and your server - Sometimes, people are telling that Xoops is rather slow and it can be true but there are ways to improve things.

Instant Zero is in charge to maintain some websites using Xoops, so we decided to share with you our knowledge in this domain and we hope that you will find it useful.

In this article, and in 5 points, you are going to see what you can do for your site.

The tips given discuss how to make tweaks to your server, XOOPS, the database, files used, and the CSS to help optimize your XOOPS site. As usual, some of these same techniques can be applied to more than just one content management system.

Victor Kane: VPS! Getting Drupal up and running on a linode

Honestly, I'm not trying to put so much focus on Drupal when you consider CMSReport.com is a site that is supposed to put focus on at least 29 other content mangement systems.  It's just that there is so much coming out from the Drupal community that it is hard to ignore.  The latest is Victor Kane's experience with setting up a virtual private server (VPS) for the Drupal CMS.

Well, after realizing the limitations of shared hosting for Drupal development, I decided to go with the big boys and use a dedicated server or VPS solution, at least for development. So I can make a multisite install for the docs and I can make subdomains for each development site.

So after perusing various options, I decided for linode. After checking out the various plans, I decided on the Linode 300, and got 50% more disk space by paying for a year.

The good news for non-Drupal users, is that the VPS how-to can easily be applied to other CMS applications.  Check out the complete story.

Sitepoint: Cache it! Solve PHP Performance Problems

"In the good old days when building web sites was as easy as knocking up a few HTML pages, the delivery of a web page to a browser was a simple matter of having the web server fetch a file. A site's visitors would see its small, text-only pages almost immediately, unless they were using particularly slow modems. Once the page was downloaded, the browser would cache it somewhere on the local computer so that, should the page be requested again, after performing a quick check with the server to ensure the page hadn't been updated, the browser could display the locally cached version. Pages were served as quickly and efficiently as possible, and everyone was happy."

Complete Story

Syndicate content