Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Book Reviews

Drupal 7 85

Posted by samzenpus
from the read-all-about-it dept.
Trevor James writes "Drupal 7 is currently at beta 1 stage with 11 critical issues remaining to be fixed before an official release version. The question arises whether we should all be writing about Drupal 7 now and so soon, when it's still in its beta phase. I argue we should be writing about it. It can only help introduce new users to the Drupal application and the Drupal community and get new people involved to help test Drupal 7. This will ultimately help improve the software for its official release and on. This helps to build the Drupal community of users and developers. It helps spread the word to everyone about this flexible and robust content management system. We want Drupal to be used. So this is one way of getting it out there and in the public sphere." Read on for the rest of Trevor's review.
Drupal 7
author David Mercer
pages 416
publisher Packt Publishing
rating 9/10
reviewer Trevor James
ISBN 1849512868
summary A pragmatic look at the steps necessary to get a website up and running using Drupal 7
Some nuances: most developers and Drupal users adhere to the rule that if you plan to run Drupal 7 as a production site and on a production server right now you need to be aware that there may still be bugs in core Drupal 7 that will cause issues on your site. But this doesn't mean you can't use Drupal 7. You can certainly download the beta 1 release and install it on your development or localhost server and use it. And you can improve it by using it now.

Which brings me to David Mercer's new book Drupal 7. This is the second edition of Mercer's popular Drupal 6 book, and here Mercer has had an early opportunity to update his text for Drupal 7. It's a good and important book to help promote Drupal 7 and spread the word about the Drupal project and the Drupal community to both experienced and new users. Mercer knows Drupal - remember that he's already proven himself with the Drupal (back to version 4.x and 5.x) and Drupal 6 titles previously published by Packt. The original edition of Drupal was published in 2006 so Mercer has been devoted to this subject for over 4 years.

The Drupal 7 title is good for Drupal beginners and novices who are just starting out with Drupal but it also has a wealth of information and resources for more intermediate and advanced Drupal users and developers. It gives you the full run down of Drupal core as well as details of many advanced Drupal topics including an entire chapter on the Views module. The book starts with a solid introduction to the Drupal 7 framework and community and shows detailed install instructions using the XAMPP installer. Mercer highlights the new installation profile functionality that ships with Drupal 7 (both a standard and minimal install profile) and even gives you tips on troubleshooting your install if something goes awry.

Chapter 2 outlines the details of Drupal architecture and structure including installing modules, enabling blocks and setting up menus. The highlight in this chapter are two new features in Drupal 7 that allow you to install contributed modules directly from their FTP URL/path on drupal.org; or by uploading the tar.gz archive directly via the Drupal administration interface. For anyone maintaining Drupal sites this will should be a well received enhancement.

Chapter 3 covers Drupal 7 site configuration and reporting mechanisms including setting up actions and triggers; creating shortcuts; managing the file system; configuring site performance; setting up site RSS feeds; and viewing site reports. One highlight in this chapter is the new shortcut functionality that allows you as a Drupal site admin to create sets of shortcut links for your fellow content editors and site admins. Another new feature in Drupal 7 is the ability to upload your attached files (images, PDF, doc, etc) to private folders on your site. In Drupal 6 you could restrict access to all uploaded files but not to specific files by content type (without having to install contributed modules to extend this functionality). In Drupal 7 you now have the ability to restrict access at the file field level per content type. So specific files attached via a content type can be uploaded to a private folder.

Chapter 4 explores Drupal 7 access control with a detailed walk-through of Drupal roles, permissions and user access. Mercer also includes a tutorial on using the OpenID Web service to provide single sign-on login functionality for your Drupal site.

Chapter 5 looks at setting up content workflows on your Drupal 7 site and describes all the Drupal core content types (Article, Basic page, Blog entry, Book page, Forum topic and Poll). Mercer covers content related modules including Aggregator and Book so anyone interested in setting up Web service based aggregated feeds; and multi-layer paginated content will get a lot out of this chapter. Chapter 6 deals with advanced content outlining the process of creating your own custom content types and adding custom fields; and integrating taxonomy with your content types.

Chapter 7 looks at integrating multimedia with your Drupal 7 site including images, and other types of embedded media. Drupal 7 now ships with the Image field in core so all you have to do is add an Image field to your content type. The image field now supports rotation and desaturate effects so besides scaling an image you can now rotate your images by a specific number of degrees.

Mercer includes an entire chapter on integrating the Views module with Drupal 7. The Views section even goes into detail on setting up advanced Views using arguments and relationships and shows you how to theme your Views. This is a real bonus for an introductory level book on Drupal. Anyone using the Views module even with Drupal 6 will benefit from reading this chapter.

Chapter 9 deals with Drupal theming both from the theme layer and the CSS perspectives. There is a lot of detailed information on theming using the Zen starter theme so anyone using Zen will learn some best practice theming solutions from this chapter. Chapter 10 introduces methods of integrating and using the Panels module with Drupal 7 as well as discussions of advanced theming techniques.

In general the title covers the Drupal 7 interface in much detail and points out the many new features of Drupal 7's administrative interface including the overlay admin screens; the simplified and re-named core content types including Article and Basic Page; the built-in CCK module (now part of core Drupal); the enhanced ability to install modules directly via the admin interface; and a look at the new core Drupal themes. Mercer covers best practices for deploying Drupal sites from staging locations to a production server; backup processes, and even a discussion of SEO best practice. The book even comes with quiz questions and exercises provided via the author's Web site. So you can use this title as a model for teaching Drupal 7 (and I would argue even Drupal 6) to new users. Short story - the book is loaded with good information and practical hands-on exercises.

Here's the main reason I'll recommend purchasing this book or at least knowing about it. Those 11 critical issues in Drupal 7 need to be tested, reproduced and fixed before we can use D7 on a production site and feel comfortable about with it's stability and security. We as users and developers need to help with this testing process. We can help to fix those issues by testing and reporting our findings back. This book will help us to do that by showing us how to install D7 and get rolling with it. For that I'm thankful it's been released now as opposed to 3 months from now. This is a good manual for us to use to test and bugfix this next great version of Drupal.

You know it's also just a great book and manual on using Drupal period — even the 6.x version of Drupal. You'll learn a ton about the Drupal framework from this title regardless of the version you're currently using to power your Web site.

Finally, the benefits of releasing this title now is that it will encourage both the Drupal community project and other Drupal authors to write more detailed documentation and instruction on how to use and develop with Drupal 7. We can raise Drupal 7 to a higher level by supporting its release with excellent documentation, tutorials and books.

Let's get Drupaling and help the community now by downloading Drupal 7.

Trevor James is a Drupal developer based in Maryland, USA.

You can purchase Drupal 7 from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

*

This discussion has been archived. No new comments can be posted.

Drupal 7

Comments Filter:
  • Seriously? (Score:2, Insightful)

    by KingFrog (1888802)
    Excellent! I'll run right out and install and use it...just as soon as you actually tell us what the heck it is! Your article isn't very helpful if you don't already know what you're talking about.
    • question (Score:3, Funny)

      by 2.7182 (819680)
      It is a new kind of sword based on black silicon.
    • by canajin56 (660655)
      It's a book review, not a product review. If you don't know what the subject of the book is, why do you care how good the book is?
      • Yeah, if you don't know anything about a subject why would you read a book about it? Oh wait..

    • Re: (Score:1, Informative)

      by Anonymous Coward

      "this flexible and robust content management system."

      Was this not in the first paragraph earlier?

      • Re: (Score:1, Troll)

        by lgw (121541)

        WTF is a "content mangement system"? Is this Drupal thing one of those toys people who can't program use to create web sites? (Not trying to troll, I genuinely don't know).

        • Re:Seriously? (Score:5, Insightful)

          by eln (21727) on Wednesday October 20, 2010 @02:58PM (#33965404) Homepage
          It's a tool people who don't want to bother with programming their own website can use to build their own website. I've been a programmer for years, and I have done web development, but I really don't want to deal with the aggravation of programming my own site (the cobbler's children have no shoes and all that). So, I use Drupal to do it for me. Sure, there's still some effort in getting things to work right, and it's never going to win any awards for innovative design, but it's about a hundred times less irritating than doing everything from scratch.

          I do have to question the wisdom of the submitter when he suggests the perfect way to get new people into using Drupal is to have them help test Drupal 7. That seems like exactly the wrong way to do it. If someone who has never seen Drupal before is first exposed to it via a buggy development release they're going to throw it out in frustration and try something else. Betas are for people already interested in and/or using your product, not for people you're trying to convert.
          • by lgw (121541)

            Hmmm, I thought Wordpress was the tool of choice for blogginabout funny pictures of your cat? But I guess I get what you're talking about - thanks!

            • by BitterOak (537666)

              Hmmm, I thought Wordpress was the tool of choice for blogginabout funny pictures of your cat? But I guess I get what you're talking about - thanks!

              Just as there is more than one web browser (IE, Firefox, Chrome, Opera, etc.), more than one operating system (Windows, OSX, Linux, Solaris, etc.), more than one word processor (MS Word, OO, etc.), more than one desktop publishing program (InDesign, QuarkXPress, MS Publisher, etc.), there as also more than one CMS, and many have overlapping functionality and overlapping niches.

              The big three names in opensource CMS's are WordPress, Drupal, and Joomla. They certainly overlap in functionality, and for many si

          • by shugah (881805)
            Yes - in the same way that GCC is a tool for programmers who are too lazy to write their own compiler.

            One off re-implementations of commonly used tools is a waste of programming time in most organizations. Why would anyone write a content management system (CMS) from scratch? A web site is a communications tool for organizations. It is not reasonable that everyone in an organization who needs to communicate with the public (or internally on an Intranet) be a programmer or have their content implemente
          • by akayani (1211810)
            That's what science is all about standing on the shoulders of those that have gone before you. Drupal is a fantastic example of that.
        • Re: (Score:3, Informative)

          by KingMotley (944240) *

          eln is basically correct, but a good content management system does so much more. Typically you can create templates for use in your site (some you can program with code, PHP, asp.net, etc). Then you use those templates to allow users to create pages for the site, say you want to create a site like newegg or amazon, you have a basic template for displaying items (picture, summary, details section with 3 tabs, user comments/ratings, etc). Then a user can input the item code, description and upload a pictu

        • by silanea (1241518)

          WTF is a "content mangement system"? Is this Drupal thing one of those toys people who can't program use to create web sites? (Not trying to troll, I genuinely don't know).

          No. It is one of those mature software packages people who do not want to reinvent the wheel every time they have to create a website use so they can focus on programming those parts that are actually unique to one website.

      • by KingFrog (1888802)
        Come now - the point of the summary is to summarize. The summary does a remarkably poor job of that. Just for reference, I have a content management system under my bed. It's a bunch of plastic containers on wheels...
    • Re: (Score:2, Flamebait)

      by yelvington (8169)

      I'd point you in the direction of the Google, except that you might need an explanation of what that means.

    • Re: (Score:2, Funny)

      by Anonymous Coward

      It says "this flexible and robust content management system". I'm going to go ahead and make a huge guess that it's come kind of content management system.

    • by mike260 (224212)

      When you read an article that assumes knowledge of something you've never heard of, why not treat it as a prompt to go learn something new, rather than a personal affront?

      • by KingFrog (1888802)
        *sigh* there is no room for humor, or the pointing out of small issues, anymore on the internet. I cry a little tear. ALL I was doing was pointing out - DUDE! If you want to post some huge-ass thing about this software, take ONE SENTENCE SOMEWHERE and tell us what it is. That's all.
  • I can tell from the book title it's something to do with websites, but it hardly helps to "spread the word" when you don't even mention in TFS what Drupal is or does?

    • by VValdo (10446) on Wednesday October 20, 2010 @02:01PM (#33964536)

      Drupal Drupal ... Drupal. wft is Drupal?

      Sounds like you're singing The Drupal Song [youtube.com], which conveniently explains what Drupal is while infecting your brain. (Unplugged [youtube.com]).

      Or you could try Wikipedia [wikipedia.org].

      W

    • by oatworm (969674) on Wednesday October 20, 2010 @02:02PM (#33964570) Homepage
      Let me Google that for you [lmgtfy.com].

      Seriously, though, Drupal is one of the more popular web content management systems out there. You can think of it in the same space as Wordpress, Joomla, Plone, Alfresco (sort of), and so on. The idea behind these systems is to build web sites and manage web site content without having to hard-code everything. Each system does it differently with different focuses on specific parts of the web site content creation process. Wordpress, for example, is a moderately simple system that's popular for blog creation - though it has some extensibility, ease-of-use has always been its primary goal. Drupal, meanwhile, is sort of the "Linux" of the web site creation world, in that you can customize it via specialized modules to make it do whatever you want, but it doesn't do you a whole lot of favors right out of the gate. Joomla is probably closer to Drupal than Wordpress, Alfresco's primary goal is document management (automating workflows, permissions, etc.) so it treats web content accordingly, and I don't know enough about Plone to talk about it even remotely intelligently.

      So there you go.
      • Re: (Score:1, Flamebait)

        by Hognoxious (631665)

        You can think of it in the same space as Wordpress, Joomla, Plone, Alfresco (sort of), and so on.

        So basically, it's a fuming great big pile of shit?

        • Re: (Score:1, Troll)

          by eh2o (471262)

          Yup, the biggest of them all.

        • by oatworm (969674) on Wednesday October 20, 2010 @02:29PM (#33964968) Homepage
          Yes, in much the same way that Linux, Mac OS X, and Windows are fuming great big piles of shit compared to a set of skilled engineers hard-coding in machine code against a motherboard.

          They're generalized solutions to complex problems. Like all generalized solutions, they're more bloated than a more specialized solution for a specific problem because they contain code that solves problems you don't necessarily need solved. On the other hand, they usually take less time to deploy and they might solve a few problems that you don't even know you have.
          • Re: (Score:1, Flamebait)

            by Foofoobar (318279)
            nail on head. I tried to help[ a site that was getting thousands of hits a day but had built their entire siter on Drupal with it's homemade version of ORM. They needed lots of many-to-many tables and everytime you do that in a NORMAL RDBMS, you only need two tables and one joining table. But in Drupal's infinite Wisdom, it creates 5 tables to do the same thing and similar situations with one to many. Over time your database becomes a nightmarish solution to manage and is sluggish and slow due to a poorly a
            • by oatworm (969674)
              Right, 'cause it's creating the overhead it needs to convert those tables into objects that Drupal understands (nodes) and mapping the relationships between those objects using methods that Drupal understands (taxonomies and such).

              Right tool for the right job and all that.
        • by drinkypoo (153816)

          I can't speak to daily maintenance but I can tell you that it's easier to get up and start producing actual content on a site that looks like what you want with Drupal than with any of those. Drupal has had some huge wins lately in taking over sites, like The Economist.

          The maintenance is pretty easy too except that upgrades are insufficiently automated.

    • Wow, this is like the 4th Drupal book review on Slashdot in less than a year. I've never tinkered with it, but I've yet to talk to anyone who has had any problem getting it up and running, let alone needed a book. How about a few book reviews on something we aren't familiar with?

      • Wow, this is like the 4th Drupal book review on Slashdot in less than a year. I've never tinkered with it, but I've yet to talk to anyone who has had any problem getting it up and running, let alone needed a book. How about a few book reviews on something we aren't familiar with?

        The learning curve for Drupal was more than I could be bothered with. I ended up going with Wordpress and had my site up and running within half an hour.

        • by drinkypoo (153816)

          The learning curve for Drupal was more than I could be bothered with. I ended up going with Wordpress and had my site up and running within half an hour.

          That's funny, I couldn't get Wordpress to install by following the instructions, and had Drupal up and running within half an hour. I've been running it for years now. Useless anecdotes FTW!

  • by pablo_max (626328) on Wednesday October 20, 2010 @01:53PM (#33964394)

    This seems an awful lot like an advert to me. Should it really be on the front page?

    • by blair1q (305137) on Wednesday October 20, 2010 @02:07PM (#33964660) Journal

      There's a fine line between "product news" and "astroturf".

      Hint: if you local news channel is doing an in-depth week-long series of segments on botox, you can bet they didn't film or write a word of it, and aren't relying on ad revenue to pay for it.

      • Re: (Score:3, Interesting)

        by Desler (1608317)
        It's bit too convenient that there are all these reviews of Packt Publishing books coming out from one off reviewers giving the books 9/10. If it smells like a shill review and reads like a shill review it's probably a shill review.
  • What is Drupal? (Score:3, Insightful)

    by Manip (656104) on Wednesday October 20, 2010 @01:55PM (#33964432)
    What the heck is Drupal? Are we meant to know? I've never even heard of it?
    • Re: (Score:3, Interesting)

      by Anonymous Coward

      Drupal is a php web framework, and the bane of a server admin's existence if you are supporting lots of installs. Upgrade paths are historically long, painful and confusing, EVERYTHING is stored in the database, so if something messes up in the DB, errors are obtuse and not helpful.

      I've heard of companies running it well if everyone is competent, but it's a nightmare supporting a myriad of installs with many half-competent users.

      • by phyrz (669413)

        For managing lots of Drupal sites (even across multiple servers) try the Aegir project, its close to a 1.0 release but is stable enough for production use now.

        http://groups.drupal.org/aegir-hosting-system [drupal.org]

        Kind of related, check out Drush, which lets you manage drupal sites from a linux command line & drush_make which lets you create make files for drupal sites.

        Drupal is very powerful, but its not for the faint-hearted.

    • What the heck is Drupal? Are we meant to know? I've never even heard of it?

      OK... who are you people? ;)

  • The last major release (6.0) was in February 2008. The Drupal 7 core has been rewritten heavily along with the UI, particularly in the area of the database interface and content storage. I wouldn't be surprised if the final 7.0 release will be almost three full years after 6.0, but as far as I can tell the wait will have been worth it.

    • Re: (Score:3, Insightful)

      by fremen (33537)

      I've been telling people that Drupal 7 is coming real soon now for two years! We've developed and redeveloped entire sites, all the while hearing from our developers that Drupal 7 was coming out and that we would need to think about our upgrade path.

      As far as I can tell it's vaporware. Release it already.

      • The unstable version is pretty solid, and only has a handful of significant bugs remaining, so it's not vaporware.

        However, I agree that the release cycle has been stretched way too long. There should have been at least one, possibly two major milestone releases in 2009-2010. People tried to squeeze too much into this one release.

        One problem I can identify in hindsight is the mistaken belief that the introduction of unit testing would shrink the post-code-freeze time by making regression testing easier. Inst

        • by drinkypoo (153816)

          However, I agree that the release cycle has been stretched way too long. There should have been at least one, possibly two major milestone releases in 2009-2010.

          Why? Drupal 6 is working fine.

  • Don't bother (Score:5, Insightful)

    by kc8jhs (746030) on Wednesday October 20, 2010 @02:04PM (#33964616)

    I think it's getting kinda ridiculous how authors and many books about Drupal 7were pressured into publishing early. There have been books published about software that didn't even exist at time of publication, such as Panels for Drupal 7 (they used the version from 6). Several others are publishing when there are APIs being changed to fix critical issues, and tons of new API additions still occurring. I am not even sure if Drupal 7 is in string freeze yet, and I know that visual considerations to the new themes are still on the table as well, causing all screenshots and reference to onscreen options to be at risk of being outdated. I wouldn't buy or recommend any Drupal 7 book that comes out before the release.

    I was in talks over a year ago with an acquisitions editor at a another major publisher that had only done 2 Drupal books at the time, and they wanted to get started on Drupal 7 books early since they say that Drupal books were really picking up (or that their competitors were putting lots of energy into Drupal books). The problem was, that the folks of course know nothing of the open source software ecosystem and require deadlines and schedules which are simply impossible to predict with volunteer software development. My editor wanted to have my chapters by March of 2010, so they could hit the shelves and announce at DrupalCon San Francisco in April. They were convinced that a release of D7 would happen in Fall of '09. I told them, that the release would never happen in 09 and probably not in Q1 of '10 and that getting a comprehensive API reference (I was estimating around 800-900 pages) by that time would be a stretch. They ended up passing on the offer, since they felt the timeline was wrong, and that Joomla and Wordpress downloads were better.

    I am also sick of all these books that cover Drupal 7 or other similar software are a very cursory level. I'd much rather wait for Pro Drupal Development 3rd edition to come out, when it's a book whose authors have spent thousands of hours maintaing community contributions, and they have hundreds of patches to Drupal itself.

  • 11 critical issues (Score:3, Insightful)

    by vlm (69642) on Wednesday October 20, 2010 @02:16PM (#33964790)

    What are the 11 critical issues? Or more precisely, could they ruin the book?

    I can imagine, perhaps, one of them being RSS feeds written in Klingon with backdated pre 1970 timestamps having the wrong rules of Klingon punctuation. That's all very fascinating, but since I don't care, I won't mind that the book doesn't cover that particular critical issue.

    But what if one of the 11 critical issues is some deep core framework type of thing that will require changes in everything?

    Inviting a newbie to learn on a buggy system just annoys the newbie. So unlike the review, I'd suggest a newbie learn on a fully patched version 6 Drupal. Getting stuck and not being able to figure out if its my code or a Drupal 7 prerelease bug is an excellent recruitment tool for RoR, not for Drupal 7.

    • Seriously, acting all mysteriously won't help us.

      Is it stuff like record locking issues, mishandling of input strings so that it's so hackable a Chinese baby could hack it, or is it stuff nobody cares about like field locking or only being able to run on machines that have less than 64 cores on an 8 blade server and not addressing more than 2000 terabytes of memory space.

    • by petes_PoV (912422) on Wednesday October 20, 2010 @02:47PM (#33965256)
      I can't say what the critical issues are with drupal 7, but from my experience of drupal 6 - their most critical issue was they relied on modules written by amateurs who couldn't be bothered to correct their mistakes when they came to light, making many of the modules I wanted to use useless. The degree of amateurishness was such that I spent days or weeks under the (false) impression that it must be me who didn't understand what I was doing.

      On that basis, I have no intention of porting across to drupal 7 for at least 6 months - maybe longer, until the 11 known "critical" errors have been fixed and all the so-far undiscovered critical errors fixed. Once bitten.

      • ^this. Gosh, darn, almighty is that true.

        Also, no connection pooling. When I googled on it, I got lots of references to using Tomcat (true story).

    • by yelvington (8169) on Wednesday October 20, 2010 @02:51PM (#33965320) Homepage

      The list of issues currently blocking a release candidate [drupal.org] is publicly available.

      • by vlm (69642)

        OK, so "Security harden stream wrappers by defaulting them as remote" sounds like a major one, "Cannot install on PHP 5.3.2" sounds like it would be hilarious for newbie abuse aka RoR recruitment, and "Do not enable the management menu by default" sounds like one of those "Klingon language RSS bugs" that I mentioned.

        So are stream wrappers a pretty big topic in the book and if so is this a dealbreaker for buying the book?

        • by drinkypoo (153816)

          So are stream wrappers a pretty big topic in the book and if so is this a dealbreaker for buying the book?

          Why not try reading the fine issue [drupal.org]? They're just going to change them to default to remote type instead of local type. A tiny change really, which needs to be rested regressively hence becoming a big deal in the queue.

    • The issues are critical because they are blockers to releasing a polished product. There will be no fundamental API changes. And chances are that most of these won't affect you in any way if you build a site using Drupal. Drupal 7 is already being used on production sites - some of them quite major - but we can't yet recommend you use it. The list of issues at the moment is:
      • "Do not enable the management menu by default". This is about removing some on-screen duplication that wastes pixels.
      • "Cannot inst
  • I read the summary, and all I see is someone looking for excuses to talk about Drupal. Please, talk a bit more about the beta! I'll read the article, don't worry, but please give me something tangible.
  • Other than that, my main objection to this review is that it lacks sufficient keywords so that anyone could figure out what it does.

    Keywords are your friends.

    Proselytizing won't work if you don't say what it does.

  • CMSs are Evil (Score:1, Insightful)

    by Anonymous Coward

    >>The question arises whether we should all be writing about Drupal 7

    Don't. CMS's are evil and lull "designers" into thinking they are developers and cms developers into thinking they are programmers, snarf, snarf!

  • I'm planning a new Drupal installation, and will be using Drupal 6. Even if 7 was released today, I'd still go with 6. The fact is that as a Framework, Drupal's strength is in its contributed modules. While many of the most popular contributed modules pledge to have a Drupal 7 version on release day, I expect that roughly half of the modules I want will not have a Drupal 7 release for up to a year. Not to mention the inevitable headaches from version *.0 of any software. So while it's nice to think about ho

  • I really wanted this book since I'm a Druapl user and want to find out about the upcoming changes / features in Drupal 7. I found out that the Packt Publishing website has a special going... and I was able to pick up the electronic release for $9.99. I bought myself a copy. They let you download a PDF that has your name and address embedded in the footer of each page. I like to have printed copies so I fired it off to the laser printer. Great value. Of course you can order the print version, or the pr
  • And while the odds are it will be released sometime soon, it's going to be too late. They cry for help over there. They scream when you point out a bug. So I tried to help. I posted a few patches, on active issues. I opened new issues and posted patches. Ignored. Totally.

    And the bike shedding? Holy crap.

    And look out if webchick makes a decision that affects 1000s but scratches her itch! I don't know how sun and chx do it, commit to core that is.

    Prediction: Drupal 7 will launch sometime soon, but i

    • Hear, hear. I especially like the series of bugs that they refuse to acknowledge because they think that's how it should work. Look people, I don't care if you categorize them as "intentional design flaw bugs", they're still bugs.

  • Well, let's hope they are better at keeping up with PHP versions with 7 than they were with 6. Using Drupal 6 with PHP 5.3.2 was worse than any beta I have ever participated in. Core features failed, plugins would not run, things just did not work. Still it was the most promising environment we have encountered for integrating Lucene, Solr, and Alchemy for an advanced NLP research workstation. If 7 is well behaved enough then we may even attempt a GATE integration.

Science and religion are in full accord but science and faith are in complete discord.

Working...