Deprecated - Drupal core

I've lost my way somewhere. I wanted to give a certain role permission to update all pages within a certain category, no matter who created them.

I have taxonomy_access for the category part... but it looked like I needed an 'edit all pages' permission first.

So I decided to try my very first patch...

I have installed Drupal 4.7.x beta version .Then i installed Image module from CVS.Now when i upload any image it is displaying the following message

Make sure you have a working image toolkit installed and enabled, for more information see: the settings page

But the image is getting uploaded and we can view it also.But every time we upload or Edit a image this message keeps comming
kindly any one help me with this.

Would the module_invoke_all('taxonomy', 'delete', ...) be better placed before the taxonomy module deletes from the vocabulary and term tables?

Reason I'm asking is that, if you've got a node-based module that uses taxonomy internally (ie. forum) then you need to store tid elsewhere (not just in term_node) for the sole purpose of being able to delete nodes when the parent taxonomy term goes away (at least, this seems to be the only real good reason for forum to need its own separate table).

How can I read the Drupal code, starting with the first document? I'm stuck on a problem, and I thought I'd familiarize myself with how Drupal is set up by reading the code. (I'm using civicspace.) I don't know php but I know another language, and I thought I'd try to figure out the code with the aid of some php reference books.

Can anyone explain why Drupal sites end up with such large css files? Some Drupal.org pages have 35K+ in just the css file. Why so big for such a simple theme and layout is beyond me. A Drupal forum search returns nothing useful.

I've recently been recruted to build an artistic Drupal template, which means I'll need to do quite a bit of css/php template work. I know graphic design/css/xhtml & php output. Just wondering what I'm getting into. Textpattern & Joomla templating was a breeze, but I'm not sure about Drupal/CivicSpace.

I'm experiencing an interesting situation on my site and I've been able to repeat the symptoms on drupal.org. You can follow along with these steps if you are interested.

1. Login to a drupal powered site with caching enabled
2. Click on a link that will take you to the home page (the druplicon in the case of drupal.org)
3. Notice that the home page displays the login block as if you are not logged in.

I disabled the cache and the problem stopped occurring. This could lead to potential usability issues.