Drupal social publishing software

Drupal is a powerful content management system and framework that makes building powerful websites possible for mere mortals. Some of the posts here will be syndicated to Drupal planet.

Four letter word

Stop asking when things will be done and start contributing is one of the messages in Bert Boerland's post Done is a four letter word on the Drupal project. There is a lot of truth in what he says. Open source projects like Drupal are made better with more cooks, not less. This is true. As there usually is, however, there is more to the story.

Backtracking the Drupal project the code freeze for the next release (4.7.0) was scheduled for September 1 and then pushed back to September 15. In the same announcement it was noted that a 4.7.0 release might take "several weeks" after the code freeze. And, now several months later here we sit without a released 4.7 and little progress. Though the latter bit, about little progress, isn't correct. The feeling to many people, namely the many folks implementing Drupal on servers around the world, those folks checking to see if this next great version of this great tool, don't see much progress. November came and went with more hopeful talk and now we're into the new year with Beta 2 aging a few weeks.

While it can be really frustrating watching and waiting, helping out in the forums etc. the frustrating part is feeling like little progress is being made. The truth is that gobs of work are being done each and every day. However, if like many Drupal users you don't get into the nittiy gritty details it seems to be posts every few months, or weeks, that speak optimistically of an upcoming release punctuated by waits that grow ever longer in the mind's eye. While it takes a little digging at least with open development processes you can see proof of progress if you take the time to look for it. On the other hand with closed development processes it's a different deal.

Dealing with malformed atom requests in Drupal

Recently a mostly annoying occurrence was filling up my log files with errors. The problem seems to be with some atom news readers. The standard atom feed for this site would get turned into a request that would be "/atom/atom/atom/atom".... and so on. Often longer than Apache knew what to do with it.

So, a single line added to the httpd.conf file solves the problem.

  RewriteRule ^(.*)atom/atom(.*)$ - [G,L]

Now the request is met with a 410 error - resource gone. With a little luck this will lead the coders of the errant software to start picking up on the problem.

Updating the Drupal archive module for 2006

If you clicked on the calendar archive to the right of the page in the last couple of days you'd notice it didn't allow you to choose "2006" articles.

A quick change to archive.module and all is well. The line in question is this line:

  $years = drupal_map_assoc(range(2000, 2005));

By changing the 2005 to 2006 it again works. However a better solution would include a bit more code that checks for the current year and makes it go through the current year. To save cycles the current year could be specified in a configuration file or stored in the database though each of those has their own issues associated with it.

Friday!!!

It's finally Friday. The end of the National Finals Rodeo is this weekend. Not having taken time off this week the weekend will be full of working on projects including doing some testing of the new Drupal beta.

Busy times

Sitting down recently we planned the calendar into the next year. It is hard to believe Thanksgiving is just a few weeks away and another couple of weeks fall finals will be upon us.

Part of the reason for the dearth of postings here has been working on a couple of other sites. We've been working with the new version of Drupal and really need a status update on Drupal 4.7. The code freeze announced for September 1 hasn't happened yet. There is a presentation from the Amsterdam conference but as I read the notes for it I get a code freeze at the beginning of November and release candidates rolling around November 18. Hopefully more news will come soon.

Frustration with IE 6

It has been a frustrating day trying to deal with the CSS bugs in Internet Explorer. This site shows up nicely in Firefox, Safari and other browsers using CSS style sheets to handle the display. However if you're looking at this site in Internet Explorer 6 the sidebar doesn't show up. The bmannconsulting.com site has the same problem (and is another Drupal site). Is there something in the default Drupal .css that causes this or is it some oddity of IE we're left to battle on our own. It might be necessary to re-design the CSS with the advice from webreference.com. Something to do this evening I guess.

OS X 10.4 vs. Drupal Mailhandler

After upgrading from OS X Server 10.3 to OS X Server 10.4 the Drupal Mailhandler stopped working on the server. Clients could login and get mail no problem. Even Squirrelmail worked flawlessly.

However when the mailhandler module would try to login the response in the error log was:

TLS server engine: cannot load CA data
TLS server engine: No CA file specified. Client side certs may not work
STARTTLS negotiation failed:

A few sites suggested permission problems with the /etc/certificates directory but that did not seem to be the problem in my case. Ultimately it was fixed by going to Server Admin's general settings and re-creating the server's self-signed certificate.

Publish and subscribe

In response to a post a few weeks ago somebody commented that I should check out the publish and subscribe projects. I did and they are very good. The publish module, in particular, is just what I'm looking for. For my needs the subscribe module is not quite what I'm looking for. Two things:

The Publish server needs to be able to be any computer. With the current setup there is a need to input the name of the publish server. While this is possible and dealing with publishing from laptops can be handled with dynamic DNS. What cannot be handled is when the publishing server is NAT'd on a shared internet connection.

Within the subscribe module the customizations to make it less apparent where the content comes from (i.e. when it's a backend server not one that you want to be visited by the public) is a process of customizing the module. It could really use these as options in setting up the channels.

Using Drupal for brochure style sites

There is a thread going over at Drupal.org about the best way to use Drupal for a brochure style site.

Dries makes the comment that a needed change is the ability to, per-node, limit the inclusion of author and date posted information. I agree in part. It would be good and likely would be good in Drupal 4.7 which has much better dynamic hiding and showing of parts of the authoring screen. One of the common complaints I get from users is that the screen for authoring posts, especially if a user has many privileges is that the authoring page gets confusing.

Upgrading to PHP 5

I've been working on some Drupal installations the last few days. First off I've started working on the Drupal-CVS version that should soon be Drupal 4.7.

One of the modules I've been working with is publish. The Publish module as it's out in CVS doesn't work well with Drupal-CVS because of changes to the methods for handling nodes. It also has a construct that doesn't work with PHP 5.

The error is "Cannot use object of type stdClass as array". The required change is to change unset ($class['property']); to unset ($class->property);

So the patch is on the Drupal Publish project page.

Pages

Subscribe to Joshua Brauer: All Drupal items