Post installation

I'm looking for a way in the glossary module or taxonomy to disable a glossary vocabulary for all users but still allow admin to add to terms/see glossary or a way to just lock out selected user roles from seeing specified (not all) parts of the glossary.

I've already tried out taxonomy_access and it didn't work out for me because I had to select terms and not entire categories - with 600+ terms that'll get messy when I want to do anything as far as access goes.

I searched for about an hour today trying to find a solution to this problem and I came up with a ton of things, that were just slightly different than my situation and none of the solutions helped. My problem is that custom multi-level menu items won't expand at all, no matter what I do.

Installed Drupal 4.5.0/Civicspace 0.8.0 at www.antnottv.org
Having trouble updating user information and cannot approve user registrations. Here is the error message it gives me each time I try to update one of the user accounts:

Is there a way to prevent people from assigning a new content item to a root taxonomy category?

For instance, if I have the structure:

Images image edit vocabulary add term preview form
General Images (edit term)
-- Misc Images (edit term)
-- Story Images (edit term)
-- Travel Images (edit term)

I'd like for people to not be able to assign a new image to General Images.

Make sense?

Skorch
www.gonzotravel.net

i only want stories published to the front page.
pages i want to use a special pages: lists of people in a group, info about a project, etc. these will usually be accessed via a block, a story, or another page (and as part of books).

how can i set the default for pages to having "publish to front page" be de-selected?
(and can i do that for events, btw?)

how can i keep pages from being trimmed? this is unnecessary if they are not appearing on the front page?

thanks

I recently installed drupal 4.5.and I was trying to use the inline module to get images to display with the nodes. I'm using the 1.2 version of the inline module from November 22nd. It works when I display the story but the teaser is showing "[inline:1]". It's got me puzzled since the changelog specifically talks about this bug being fixed.

I've tried it with clean urls enabled and disabled and it doesn't seem to make any difference.

I've tried searching through the forum but without any luck. I'm hoping can tell me the dumb thing I've probably done. Thanks!

Linda