Deprecated - Drupal core

This information is out of date. For a current list of outstanding issues, visit the project's issue queue.

Hey all,

I've received various requests for information about the Content Construction Kit project, and it's time for a summary of the work so far and what's left to do. I'll keep this topic updated with the development progress; feel free to post questions and feedback as replies until such time as there's an official project created that can take issues.

Related information:

hey all, i have a kinda wierd question, well, as most of you probably know, when you reply to a comment instead of adding a new comment to the forum topic, your reply is slightly smaller than the one you replied to. and alas, this is becoming a problem as my forum topics gradually get longer. is there a way to make ALL the comments the same size?

When an Admin creates a new account under 4.5 ... they get this message:
Created a new user account. No e-mail has been sent.

Is there a patch out there that allows the Admin to send a welcome message to this user, or a bulk select to send to several.

Secondly... It would be ideal if a 1st time welcome message would include a link like:
http://yourdrupal.com/user/new/49857237465126374859937

I have seen this issue several time out there but no real solution.

Problem:
Any user can force another user's password to change... simply by selecting "request new password" and putting in their username. The user gets an email with the new.. but this feels like a violation to the user... and a pain.

Solution?
If someone requests a new password... Don't blindly change it... send an email that says...."Is this a real request authorized by you? Click here to confirm otherwise disregard this message"

Hello to the core development team

I am new with Drupal, so i don't know how everything works and what are the habbits when an upgrade is provide.
I just upgrade the CVS version from 4.52. I can't make the module forms working because the function check_query() is no more supported.
Is there a backward compatibility when the core upgrade ?
What are the new functions modified in this CVS which need a module upgrade ? (Is there a doc ?)
What is the new function for check_query() ?

thank you for all your work and for a reply

Nicolas Penel

In the RC release thread, the following discussion arose:

http://drupal.org/drupal-4.6.0-rc#comment-31276

I had a minor problem with a feature disappearing on me - in this case, the Categories block. While the fix was relatively easy, I can imagine this kind of issue happening on some other sites where the feature removed might be a bit more complex with a fix that's not so obvious.

There were three problems, in my opinion, with how this change was handled:

1) There was no indication on the site that this feature was being removed.
2) There was no suggested alternative on the site.
3) (less of an issue) There was no period to allow users to phase out or replace the feature.

Drupal is a moving target and its back end and front end are always improving and changing. What I don't want to encourage is stagnation of either old, unused features or a bad architecture. However, there needs to be a graceful way to help users make the transition from one Drupal version to another. If we don't do this, users will soon be afraid to upgrade Drupal, and then the community will have to deal with the issue of having a dozen unsupported versions of the software that people are continually asking for help about or requesting features for.

While I posted a number of (poor) suggestions in the thread above, I might suggest instead:

For every single CVS change log made, a reference to an issue must be made.