Форумы / Cotonti / Core Labs / Ideas / Feature requests for 1.x branch

Two separate issues:

• There are only two Drupal versions supported at a time. As Drupal 7 has been out for some time, Drupal 5 is no longer supported. That means no security updates and potential compatability issues. (For example, Drupal 5 will not run on PHP newer than that version 5.2.x.)
• While there is nothing that says an old custom module cannot be maintained, they tend not to be. Lack of core fixes is part of that and another is that improvements may take advantage of core features or other modules that don't exist in an older version.

My "disaster" was that my Drupal-5 based site was running on shared hosting. One morning, at about 5AM, the hosting company decided it was using too much in the way of resources and turned it off. They didn't tell us until 2 hours later -- after I asked for help trying to figure out why it was down. (I am pretty hacked off about this as the site traffic had been pretty stable for at least the last year.)

In any case, I needed a quick fix. I had another shared hosting account. While I knew it wasn't the right long-term solution, it was the quick fix. I moved it, got DNS pointed, ... Got bit by the default PHP 5.3.x issue. Fixed that. Now, they "automatically" decide if you are using too much in the way of resources and turn off your database connection "for a while". The result is regularly broken tables. It also means attempting to move the site pretty much guarantees it goes down because of all the accesses for the dump.

Right now, all the image galleries are broken as a result of getting automatically shut down during an upgrade. Now, most of this is not a Drupal issue but it's reality. In the mean time, we had been looking at how to get to Drupal 7. Looking for over a year. Ignoring the migration issue (migration tools only handle going up one major release and we need to go two) Drupal 7 has some serious changes which make our current photo gallery approach not work. So, we remain in limbo with a limping site.

I mentioned the "too many choices" issue for modules. Here is an example. There are (at least) two different modules to add WYSIWYG editing to Drupal. One supports a specific editor, the other supports about six editors. For a site I am working on (that will probbly become a Cotonti site instead of Drupal), I picked the first one, figuring it was more likely to "work right". There are problems. So, I need to try out two modules and six editors to find something that works right. A clear issue of too much choice is not a good thing.