In preparation for my /Nick Lewis/ trip to Washington D.C. next month, I’ve begun to develop a module that integrates the CAP XML format (Common Alerting Protocol) with drupal’s node, location, google map, category, and CCK modules.
A very common question among users of Drupal is, "How do I upgrade to the latest version of Drupal?" Drupal releases often contain instructions for how to upgrade your site from a previous release of Drupal (for example, 4.6 to 4.7), but quite a bit of confusion remains for updrading from much older releases (such as 4.3 to 4.7). The folks at 2bits offer some advice on how best to update your Drupal site in their post, Upgrading From Old pre-4.6 Drupal Releases To 4.7. The post is short yet helpful in getting you started on a Drupal update.
After looking at the 2bits article, you'll see they suggest the use of a CVS client to install any files changed from older version to 4.5. If you're like me, your initial reaction on the suggestion of using CVS clients and applying patches is the emotion of fear. However I'm quickly finding out that there isn't really much to it. Applying and creating patches is a lot easier than you think.
So Earl Miles, tell us what you really think about Drupal's administrative menus:
Drupal’s actual administrative pages suck ass. It’s not just the organization that’s wrong, as I had actually thought going into this. Unfortunately, no, it’s worse than that. While there are some pages that are (by dint of their brevity) relatively good, there are other pages that are nearly unworkable. block administration, menu administration, module administration, access control administration are all headache-inducing pages.
While I personally don't mind Drupal's administrative menus, Mr. Miles makes some good points in his posts about what could be improved in Drupal on the administrative side. You can read more at his Angry Donuts site by clicking here. He also has a mention about user surveys and their worth. Something I would like to touch on later in the day.
Markus sent us a comment that he has a new version of the Akismet module for Drupal 4.7. Since I have yet to put up a "latest comments" block on my site, I've reposted his comments here:
Hi! Just wanted to mention that I have just released version 1.1.0 of the Akismet module for Drupal 4.7. It's been just 8 days from 1.0.0, but it was then when I realized that the moderator queue had to be improved to allow operations against multiple items. It also includes an experimental set of options to prevent DoS situations caused by certain spambots. That's it, happy blogging!
I took a look at his site, phpMiX.org, and found that he also made a few minor changes since his posted comments. As of this writing, he has released Akismet module for Drupal 4.7, version 1.1.2. More information including a changelog can be found at his site.
For our Wordpress 2.0 sites, we have been using the Akismet plugin to fight off the spam thrown at us through our comment pages. We've been impressed with the results with over 550 spam filled comments blocked since early 2006 and only two spam comments slipping by Akismet's filters. With these impressive results, we have been hoping to see an Akismet Drupal module also developed. Now both Drupal and phpBB users have access to an Akismet module for their CMS.
Markus Petrux from phpmix.org announced at Drupal.org:
I have to admit something. Before today I had never visited Nick Lewis' blog. However, I'm extremely impressed with the how-to content on his site. I'm sort of known to be theme development "challenged", so I look forward to articles such as the one I'm reading now.
The following is an excerpt of his latest article with regards to theming in Drupal using the PHPtemplate engine:
I have good news and bad news. The good news is that overriding theme functions is easy. The bad news is that every theme function is different, and there isn’t a standard proceedure of going about it — and its very easy to accidently do something ugly, or foolish if you don’t know what you are doing.
Early this Monday morning Drupal 4.7 was released. Since then, about every Drupal blog from Belgium (where Drupal founder Dries is from) to South Dakota in the United States (where CMS Report is based) has talked about the release. Here at CMSReport.com we've been testing Drupal 4.7 since Beta 1 and have been very pleased to see it through a mature released. The following "press release" was posted at Drupal.org :
After more than a year of development we are ready to release Drupal 4.7.0 to the world. More than five years, 13 major releases, 30+ servicing firms employing 100+ Drupal professionals, 300+ third party modules, and over 55,000+ Drupal powered sites later, Drupal 4.7.0 is finally here and it rocks!
The following was submitted on our sister site, Like that Idea on December 21, 2005.
For awhile now, I've wanted to build a Website focused on reporting today's news in the world of content management systems (CMS). In simple terms, a CMS is a system used for storing, managing, organizing, and displaying content. There are all kinds of CMS out there, with one that you're most likely familiar with, the Web CMS (we use one here at Like that Idea). While a CMS is more than just software, among the computer techies it is usually the software that is talked about most.