drupal

On the SitePoint PHP blog, David Peterson shares some of the comments and thoughts that Rasmus Lerdorf (creator of PHP) had recently on a good range of topics (including frameworks).

I recently came across this article:

"Apple, Microsoft, PHP headline IBM's list of most vulnerable software"

Drupal 7 is shaping up to be the most modern Drupal ever! (Now there's a silly title if I ever heard one...) Not only are we upping the system requirements to PHP 5.2 and MySQL 5.0, but PostgreSQL users will now need PostgreSQL 8.1 at least.

read more

On the Paranoid Engineering blog, there's a recent post with a "CMS battle" of sorts between two of the more popular PHP-based content management systems out there - Drupal and Joomla.

Recently I've been talking up various ideas for pluggable subsystems in Drupal in IRC and the other usual haunts.

Ideas have been percolating in my head, but so far I have been remiss in actually writing them down. Yesterday, however, I had an epiphany to solve the primary issue I was trying to work out, so I present a hopefully workable RFC (for real, not IETF version) for pluggable subsystems in Drupal.

I am posting this over to Planet PHP as well to invite commentary from those who aren't already embedded in the Drupal mindset.

:-)

Tag 1 Consulting: "With all the excitement surrounding cloud computing, and specifically Amazon's EC2 (Elastic Compute Cloud) Beta service, I decided it was time to give it a try myself..."

CMS Watch: "However, these modules could be your biggest problem as well because many times, module upgrades do not keep pace with Drupal upgrades..."

Larry Garfield talks about a new feature of Drupal 7 in a new post to his blog - the new introspective code registry that's been introduced in this latest version.

A recent thread on the Drupal documentation list has brought up once again the "why don't we have a wiki on Drupal.org?" question.

It comes up regularly; you can set your watch by it.

What I've never understood is why anyone would want to take a step backwards from Drupal's handbooks to a simple wiki.

How would removing features and capabilities help Drupal's huge pool of documentation?

What exactly makes something "a wiki"?

Let's examine:

read more

One of the major changes in Drupal 6 (where "major" is defined as "worthy of a mention in Dries' keynote") was a new feature of the menu and theme hooks.

The newly introduced "file" and "file path" keys in those hooks' respective retun arrays. allow them to define files that get included conditionally, only when needed.

In theory, that should be a big performance boost; page handlers are virtually never called except for on the page they handle, so loading all of that code on every other page is a waste of CPU cycles.