Development of the SMFforum Integration module for Drupal is no longer. Amy Stephen over at OpenSourceCommunity.org pointed out on her blog that the module's project leader, "vb", pulled the module due to licensing disagreements with SMF LLC. Amy references vb's original post at the Drupal forum, but she has a lot more to say. Amy's an active participant in the Joomla! community, a community which had their own issues with a bridge between Joomla! and SMF.
According to vb's post, an email sent by Michael "Oldiesmann" Eshom, Project Manager, Simple Machines LLC stated that:
The problem isn't with the smfforum.module file or the packages distributed on drupal.org. The problem is with the "smf_api_subs.php" file that you're distributing as part of the smf api package - it contains modified versions of several SMF functions, and you did not ask for permission to use this code or distribute it.
It appears that Simple Machines LLC doesn't have so much of a problem with bridging SMF and Drupal as much as they have issues with their own code being used without proper permission. The Simple Machines License clearly states that "Any Distribution of a Modified Package or derivative requires express written consent from Simple Machines LLC." No word on whether Simple Machines LLC would endorse the use of their code if permission is asked.
Radiant 0.6.6 was released over the weekend, shortly after the release of Radiant 0.6.5. Obviously, 0.6.6 of this built with Ruby on Rails CMS was released to fix some bugs in 0.6.5. So instead of focusing on the bugs, let's focus on what is new in 0.6.5/6 since Radiant 0.6.4 was released in November 2006.
Since Radiant 0.6.4, the latest versions of the software introduced two major changes:
Rails 2.0.2 included (0.6.4 used Rails 1.2.5)
RSpec 1.1.4 is used in core and supported in extensions
Mozilla Firefox 220.127.116.11 is now available. The update is a security and stability release and this explains why Firefox users might have been seeing more crashes than usual.
I knew something wasn't right with my favorite Web browser. You can download the latest Firefox (and Thunderbird) at Mozilla.com.
A professor says he has only one girl in a computer science major class in 2008, down from 40 percent in 2000. What happened? eWEEK gets field experts to weigh in.
While women hold 51 percent of professional jobs in the United States, they make up only 26 percent of the IT work force, according to the National Center for Women & Information Technology. Furthermore, fewer women worked in IT in 2008 than in 2000.
The article later discusses about the need to put more effort into convincing women that working with technology can be cool. This argument and others the article makes for how to get more women involved in IT and computer science is a problem. I don't know a single geek, whether male or female, that had to be convinced that technology is cool.
I have to admit that when someone submits a story and I trust them...I sometimes don't read the whole article before I publish it. So until I read Dean Barker's Gadgetopia, I didn't realize his company, Blend Interactive, was featured in eZ's SHARE! magazine. The irony is that if I had read an article posted at my own site by one of eZ System's own people...Dean's post wouldn't have been new news to me. Sigh, I have been just too busy...
Last week marked the official release of Magento 1.0, an open source ecommerce platform. Magento has been on my radar scope for some time thanks to those who have left comments about it here. Since, I likely will have need of a good shopping cart this year for a planned project, I've decided to put some focus on Magento. I will be removing Mambo from my top 30 "CMS Focus" list to make room for Magento. My apologies to Mambo fans.
A couple months ago, Technoratiannounced that users of Wordpress needed to upgrade to the latest available version (now at Version 2.5). This week, Technorati announced that blogs remaining vulnerable to identified security exploits may no longer be indexed by their service.
Because of this ongoing problem, we're discontinuing processing crawls of blogs that exhibit common symptoms of being compromised. We strongly recommend upgrading your WordPress installation. Even if you haven't been afflicted by a compromise, by the time you are aware that you have been a number of negative consequences may have already occurred (for instance, flagged spam by Technorati, Google or Yahoo!) -- this has been reported by many WordPress users.
By not upgrading your software, the search engine services may block your site from being listed. I can't think of a greater incentive to update your content management software to the latest version than the threat of being delisted. This is a bold move by Technorati. I'm personally glad Technorati is taking a stand against sites hosting older versions of Wordpress with the known security holes. In my opinion, there really isn't a good reason you shouldn't be upgrading your Wordpress site to the latest version.
Interesting, very interesting...Windows 7 Build 6519 Screenshots (December 2007). Microsoft's last chance in convincing me to keep Windows on my home machines before I become an Apple Mac and Linux only house. Surely, anything after Windows Vista would be an improvement.
The April issue of Adobe Edge contains the article, Review of open source content management systems. The article provides an overview of what the author describes as "five of the top open source software (OSS) solutions". The five open source CMS included in the author's list are CMS Made Simple, Drupal, Joomla!, WordPress, and XOOPS. After reading the article, I found myself wondering how we "reviewers" can actually improve our reviews of open source CMS. More importantly, I've come to the realization that I can no longer claim to be non-biased in which CMS I believe is the best out there.
The author does a fine job in the article describing the similarities and differences between the CMS being reviewed. However, one of the issues I have in this article and many others I've read that review CMS is the big jumps in the conclusion:
Drupal, Joomla!, and XOOPS are best for building an e-commerce site because all three offer:
Support for third-party payment processing mechanisms (such as PayPal)
Modules for shipping and sales tax calculators
Shopping cart functionality
While it is true that Drupal, Joomla! and XOOPS can do e-commerce, none of these CMS can do that straight out of the box. I can just imagine a shop owner or design company trying Drupal, Joomla!, or XOOPS for the very first time and wondering, "how the heck do I get a shopping-cart into the CMS?". While the author does hint in the article that third-party modules are needed to make the e-commerce work, I think the author would have been better off better explaining that "some work is required" to get those features into the CMS.