Drupal 4.5.0 release schedule

Use local culture conversions to display time in a friendly format but internally track only in UTC time which doesn't have a "daylight savings" issue. I am PHP ignorant but it seems they should have time libraries to deal with this.

I'm afraid I don't have enough experience with PHP to take on such a task myself.

Is there at least a way to turn off all timezone conversion and just use the server's local time by default instead?

If this comment wasn't including closing tags, the rest of comments would appear ugly...

themes are for compter geeks like you and me. I've seen this feature get requested very often since I've started hanging out here - it might not be such a bad idea.

Really, one would optimally hope for little checkboxes to turn EVERY little widget on or off. I think this is a reasonable feature request.

- Robert Douglass

-----
visit me at www.robshouse.net

The way I see it, ideally, it should work on per-node basis, regardless of the node-type. Right now, a theme based solution commits a person to side-wide implementation. Even with the "node-type" hacks where we only hide authorname from "Page" nodes, all the "Pages" in a site lose their authoname/timestamp tags. Someone might want to hide authonames and timestamps from one page, but not the other. Not currently possible.

Killes seems to shoot down this and point to "fix it at the theme" every time someone asks this. Many in Drupal have correctly defined authorname and timestamps as data elemenets. Ex: Ax's Drupal ERD, Kjartan's explanation of Nodes, spiderman's How Drupal Works. In a well built and properly designed CMS all data elements should be independent of presentation layers. Drupal is very well built, otherwise.

Ax's Drupal ERD spells out each Node's attributes. Most of which are controlled from Drupal's administrative interface. "Created" is one such attribute. But it has no controls.

In layman's terms, when someone posts a story in his or her Drupal site, the database collects 1. the username or the author, 2. time of post, 3. title, 4. path alias, if any, and 5. content/post data, the article; and then adds the controls of the story: yes/no on A. Published, B. In moderation queue, C. Promoted to front page, D. Sticky at top of lists, E. Create new revision, and F. reader comment controls. In those controls, A, B, C,and D all manipulate the data entered in 5. content. What keeps Drupal from manipulating 1 and 2 as well? Those two, 1. authorname and 2. timestamp are clearly data elements. Yet they are never controlled from the same user interface. This is not in keeping with Drupal's discussed designs (or at least what I can read in the ERD and Mailing lists) and not very intuitive for the lay users.

Now that MovableType has had licensing issues, many peole will come to Drupal. 99% of them aren't themers or developers. At some point people need to think of users and listen to what they expect and want.

The ability to hide authoname and timestamps are the Number 1 requested feature that no one seems to care about.

There were some bugs around locale translation, and these got fixed, so you should redo your tests (as Gerhard suggested).

I want node-level permissions. From what is in the current downloads section, it claims to be broken. I have tried it and it seems to work for me... but I haven't progressed further and I think I might be stuck on a certain version because of this (which is ok).
I've thought about hacking it myself, but being as it's major core hacks, mine would be fruitless on the next major upgrade (assuming it really is a major upgrade) and if I wanted to keep up to date.
I appreciate the work done so far and have convinced my business to use Drupal for a knowledge base. My goal is to have parts secret from the world and parts public. Anonymous access would be granted to the public section, registered users would be able to see thier own company's stuff (such as manuals and technical details), and employee's can access everything including our core kernel.
It works for me, but (1) I'd like to see it in the kernel so I can upgrade eventually and keep up with the times and (2) I'm sure others would like this feature as well and might help the Drupal community grow.

-----------------
"Our greatest glory is not in never failing but in rising every time we fall." -- Confusious

I had tried viewcvs already but didn't see a 4.5 branch.

I will try what you suggested. Doesn't matter if something breaks. I am not working on a production system yet. Probably will prepare the complete site and then move the database to the online server. By then I guess 4.5 should be stable.