Replacing the ecommerce module with ubercart during a Drupal 5 to Drupal 6 upgrade: could it be so easy?Sun, 2010-01-03 06:38 — victorkane
During one of the many non-trivial Drupal 5 to Drupal 6 upgrade tasks we seem to have been working on recently (pretty good success rate there I am happy to say), a client wanted to change from the e-Commerce module they had been using in Drupal 5 to the Ubercart module in Drupal 6. The constraint called for maintaining product creation dates, that is, re-cycling the product content type created by e-Commerce (v3 by the way) into a fully fledged Ubercart-integrated product node. After a few dry runs we succeeded (see script below). Could it really be so easy (comments welcome)?
As in all non-trivial Drupal 5 to Drupal 6 upgrades, we based ourselves on an in-house Gap Analysis form which leads to a customized checklist of tasks. And the first task was to replicate the legacy site on our own test server. Then, the upgrade is run on a second test instance, and each successfully completed milestone is committed to a version control system (the snapshot includes the database dump) in order to always have a solid base to fall back upon should problems develop (when problems develop). A second very useful benefit of using a version control system for each step completed is that the log serves as an admirable guide for upgrading similar sites, or should it become necessary to re-do the process.
I still have my brown Acquia T-shirt that was distributed at the March, 2009 Washington DC DurpalCon. On the back it says "Free as in beer". Well, the free bit still applies to Acquia Drupal, and the various stacks which are useful for various operating systems and environments to a lot of people. But now Acquia is mumbling in their beer: no more freebie community style accounts, you gotta start paying for site monitoring via the Acquia Network once the initial 30 day trial period ends. OK, it does include goodies like Acquia search, and other stuff. But to get a solution that is truly free as in beer, and a richer solution at that, it's clearly Nagios time for us dogs.
This is a detailed howto article, but you can skip the parts that you don't need easily, and it will get you up and running with an enviable Nagios Drupal Monitoring station. Just jump in wherever:
- What is Nagios?
- Setting up the Nagios monitoring application.
- Setting up the Nagios monitoring module (Thanks kbahey -- Khalid Baheyeldin of 2bits.com)
- Enjoy your free Drupal sites monitoring dashboard!
- Enjoy receving Drupal site Nagios alerts in your mail for free!
- What's next? Roll your own...
- Enterprise level search: Apache Solr Search Integration explored in details along with other options (Sphinx integration , and Search Lucene API and related modules
- Spam blocking server alternatives
- Centralized administrative task management
- Centralized software deployment and update alternatives, especially with drush and the Aegir Hosting System.
This short article explains how to quickly and easily add Google Translate functionality to Drupal content without hacking any blocks or the actual content itself. You simply stick it into a page template where it belongs.
But for Google Translate you do not need any keys yet and this is so simple it's hardly worth the CVS.
Project Flow & Tracker "Paris" - Part 3: Towards integration with Open Atrium via our very own branded Feature Server!Fri, 2009-08-14 19:36 — victorkane
So today finally Project Flow & Tracker meets Open Atrium, and does so in style. My friends at Development Seed just told me about the new availability of the feature server code (w00t! out just a couple of days right here: http://code.developmentseed.org/featureserver/dashboard), not to mention a spanking new theme, singular,
"a minimal theme that can be rebranded quickly and simply using background images a la Twitter. The theme comes with several prepackaged backgrounds and site administrators are encouraged to upload their own."
also out just a couple of days, and which can be found at http://code.developmentseed.org/singular/dashboard . Singular and depends on the base theme Tao: http://code.developmentseed.org/singular/dashboard (also fresh meat!).
So we will be diving right in. Here are the steps we will be taking, so hang on to your mice, it's going to be a fun ride:
- First steps with Open Atrium itself (OK, what is it?)
- First login as admin
- Creating a group
- Creating a project and some project docs
- Inviting some more team members
- Working together
- Our bare bones "Feature Machine" morphs into the stylishly themed and branded AWebFactory Feature Server!
- Feature Server
- We stick our feature onto our Feature Server
- Sticking our feature on the feature server
Time to commit our work to bzr!
- Importing Project Flow & Tracker as a feature into our Open Atrium based PFT site
- First steps for integration of PFT feature into Open Atrium
- Bringing back the full PFT feature set.
- Making PFT usable
- Using PFT to develop PFT
- Development environment
Dedicated to the compadres at #drupalcampla http://2009.drupalcampla.com/
Today we witness the birth of PFT "Paris" as a feature, that is, based on the Open Atrium compatible features family of modules which promise plug and play feature components for Drupal. It should also serve as a useful tutorial on how to get started with features (and a smidgeon of drush and bzr too!). And you can download the whole shebang and enjoy Project Flow & Tracker lite. What we'll do: