Deprecated - Drupal core

Hello,

Drupal heavily relies on the php function array_key_exists(). This function is VERY slow compared to a simple "isset($array[$key])". See notes on http://php.net/array_key_exists
I really would recommend to change all occurences of array_key_exists($key, $array) to isset($array[$key]) to make Drupal even better by increasing its performance.

Thank you,
Alex

Hello Drupal.org Developers,

I am an eager student interested in working on the Summer of Code 2005 projects for the Drupal code. I have gone through the Summer of Code 2005 proposed project ideas and noticed the Quiz module development project. Since Google is sponsoring a large portion of the stipend, I feel that the Drupal community would welcome with open arms the idea of having less experienced student programmers work on potential projects.

But first, allow me to introduce myself. I am a student at Case Western Reserve University in sunny Cleveland, Ohio, studying Computer Engineering and Art History. For this summer, roughly the same length of time that the Google Summer of Code 2005 project encompasses, I will be living in San Francisco, living a true life experience. While I do not have a job out here in California, I do have a deep-seated interest in programming and in giving back to the open-source community. I run a large number of open-source projects, both on my personal computers (I'm typing this on a PowerBook) and on my servers (which I use to host numerous sites, including my personal website at conesus.com, which utilized Apache, PHP, mySQL, and other open-source scripts).

I live and breath open-source on the compiled end. Now I'm looking to give back on the fresher code end. However, as much as I want to give back (especially with such a lucrative option coming from Google), my experience lacks in depth, as I've only programming for the local IT Help Desk at Case, writing the financial system, the payroll manager, the customer database, and numerous scripts and trackers used in conducting business. All of these are home-brewed solutions, custom written for Case.

We have put together quick instructions and a patch together to patch Drupal for people who might have hacked their distribution or prefer patching rather than download the whole enchilada. It's a complete diff between 4.6.0 and 4.6.1 and I have included quick instructions to update the database. The patch is only 18kb. It was tested on our drupal site, the site you are download it from using the exact instructions presented.

http://drupal.etopian.net/drupal_4_6_0_to_4_6_1_patch

Just got this from my ISP....re: Drupals htaccess file...anyone know if they are taking the proverbial p?

Dear Customer,

We are contacting you to let you know that a .htaccess file on your site has
some badly programmed rewrite rules which have caused the server to crash
and entirly go down.

the drupal .htaccess file they are talking about is the one that comes with 4.5.0.

Surprisingly, I can't find a Security forum, so I post here instead.

In my logs, I find the following php error messages:

Type: php
Severity: error
User: Anonymous
Message:
Duplicate entry 'menu:0:en' for key 1 query: INSERT INTO drupal_cache (cid, data, created, expire, headers) VALUES ('menu:0:en', 'a:3:{s:10:\"path index\";a:180:{s:11:\"admin/block\";s:1:\"2\";... in /path/to/includes/database.mysql.inc on line 66.

There are three similar messages in a row.
Does it look like a hacking attempt on Drupal, or else, what is it?

Last week I deleted some registered users from our site. These users had created some content (book page/story) in the past. After deleting these users, the nodes they created were not visible anymore; a n/a message was displayed instead. After changing the uid of the nodes to the uid of an existing user, the nodes were visible again.

Bug or feature?
Is the behavior as described above the intended behavior of Drupal? In our situation it is considered a bug that content is not visible because the user who created the content doesn't exist anymore.