Post installation

Hi guys & gals,
Looking for some help with img_assist module. I have extracted and added img_assist to my modules folder, and enabled it under /administer/modules

the little add image icon shows up in my edit fields, but when i click it, another box pops up and says "The image module must be enabled to use img_assist."

I have made sure i enabled the module a couple times, reset apache all that stuff, but it still comes up with that message.
I am probably missing somthing trivial, but being a bit new to all these i am looking for some quick assistance

I was drawn to Drupal because I could see the tremendous potential of using taxonomy terms to affect the way a page looks, as well as what features might appear in it. However, I'm having trouble grasping how to make full use of this and I'm hoping someone can steer me in the right direction.

I'm familiar with the concept of parent>child, but I don't understand how to work within the hierarchy.

Let's say I have several layers of terms. For example, a term "bulldog" is a child of "dogs," which is a child of "mammals," which is a child of "animals." So we have this: animals>mammals>dogs>bulldogs.

I can conceive of several instances when I'd want to make my pages appear differently or have different blocks based on levels of that hierarchy.

For example, I might want to use a different CSS for "mammals" than what I'd use for "insects." But that CSS needs to apply to all children of "mammals" as well, such as "dogs," "cats," "pigs," etc.

And by the same token, I might want to have links to pages about dogs only appear on all pages created with different children of "dogs."

So here's where I have trouble understanding: When I create content about, say, bulldogs, do I have select the terms "animals," "mammals," "dogs," and "bulldogs," or is there a way to set it up so that if I select "bulldogs," the parent terms can be assumed? If it's a bulldog, it must be a mammal, so can the CSS for mammals be automatically used without me telling Drupal my page is also about mammals?

Is there a way to have a user who is prevented from sending message to other users or posting messages in a fourm until he has had X approved posts? Also, if you want to ban a user what is the behavior? are they denied or is it possible to set it so that the user thinks they are doing everything like sending messages and forum topics but it's not really happening?

I need to display the nodes on the homepage, grouped in different zones, depending on their taxonomy, like this:

 ____________________
|    |               |
| m  |     tax1      |
| e  |_______________|
| n  |               |
| u  |     tax 2     |
|    |               |
|    |_______________|
|    | tax 3 | tax 4 |
|____|_______|_______|

(sorry for the poor ASCII art)

I thought that that the easiest way is to do it is to create a few blocks, displaying the nodes in every different block, selecting them with php snippets.

my problem is that even if I do so, the nodes will still be displayed, unsorted, on the homepage, in the "content" zone, along with my new user created blocks.

How can I remove the "default" nodes in the content zone in my home page? ( using the "Promoted to front page" check boxes is not an option, since i'm going to use them to decide which ones will be displayed in the blocks)

Is it a better way to do the whole thing?

thank you!

Everything was going pretty well, and then I decided to install Taxonomy_access_control, and ever since then, nothing has worked properly with my site. I can't even get the front page content (eg: stories promoted to front...) to show up, unless I'm logged in. The settings are OK via access control.

However, I can't even get into Taxonomy Access Control to en/disable it or check the settings. I'm pretty sure something went wrong somewhere. It worked fine for one day, then nothing. I also tried a fresh install and redid the SQL tables. Nada.

In the logs, I have this contast error:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INNER JOIN node_access na ON na.nid = node.nid UNIXTIME(changed),0) AS weekno FR' at line 1 query: SELECT YEARWEEK(FROM_ INNER JOIN node_access na ON na.nid = node.nid UNIXTIME(changed),0) AS weekno FROM node n INNER JOIN node_access na ON na.nid = node.nid WHERE (na.grant_view = 1 AND CONCAT(na.realm, na.gid) IN ('all0')) AND n.type IN ('amazon','poll','story') GROUP BY weekno ORDER BY weekno DESC LIMIT 9 in /var/www/html/includes/database.mysql.inc on line 66.

I did find some older topics about this issue but most had no solution, required disabiling of a module I wasn't using, or patching. IF the db_rewrite patch will really fix this problem, I don't understand where the patch is supposed to go (fix which file, etc?)

I installed the ecommerce module and enabled the following sub-modules: cart, ccard, donate, ecivicrm, payment, paypal, product, service, shipping, signup_ecommerce, and tangible. For some reason I am seeing 2 Shipping menu items in my Administrator menu, one pointing to /admin/store/shipping, and the other pointing to /admin/store/settings/shipping'.

The resource that they are linking to is the same. It is the shipping calculations method form.