Drupal 6.x

I get the impression that you can't upgrade from arbitrary versions to the latest version of drupal, but rather you have to step your way up one by one. So if I have a site at 5.7, do I have to upgrade to 6.0 first and then to 6.1? Or can I go straight to 6.1? What are the rules about this?

You are not authorized to access this page.

Permissions are set (node module) - access content for anonymous user. What should I check also?

I just wanted to report some possible bugs in Drupal 6.0.

It could be my theme, and not Drupal, but just in case - When I click on navigation links, sometimes it tells me the page is not found. I tried to add a menu item to point to my contact page, and it gave me that error. When I went back, all of my previous menu items were no longer in my primary links list, and I got a message that said that I didn't have any primary links yet.

I created a "Product Listings" content type and added a few relevant fields for it. But there are two problems:

One: The Author & Date show at the top, and while for stories, it's cool, I'd just assume leave that part off of the product listings.
Two: Price. I enter in, say $10, and it becomes a tag. I only want to display the price & have a field for staff to enter in prices, but not tag. Is this doable?

Hi everybody,

I have a problem with the content. There are some messages like that before I try to post in forum

- warning: fopen() [function.fopen]: SAFE MODE Restriction in effect. The script whose uid is 10025 is not allowed to access /var/www/vhosts/mf-lens.com/httpdocs/sites/default/files owned by uid 48 in /var/www/vhosts/mf-lens.com/httpdocs/includes/file.inc on line 129.
- warning: fopen(sites/default/files/.htaccess) [function.fopen]: failed to open stream: Success in /var/www/vhosts/mf-lens.com/httpdocs/includes/file.inc on line 129.

We had the need to create multiple book type content with varying access rights depending on a users role for our intranet. We also are using the Organic Groups module and the LDAP Integration module to tie in to our Active Directory for authentication. When a user logs in to the Drupal system, the LDAP Integration - Groups module automatically grabs a filtered list of that user's group membership and maps it to a Drupal roles. In order to do this on our current v5.3 system, I copied the Book module to create what I called a 'WikiBook' module. This allowed me to restrict rights on who could edit and or see specific books based on role membership. The 'WikiBook' is then used to allow everyone within a specific group to have full edit and create rights. I spent a lot of time trying to achieve this with the book module alone using various access control modules and outlines, but none worked. In the end, the easiest solution I could see (I'm sure there was an easier way, I just couldn't figure it out) was to recreate the book module as a 'wikibook' module.
The question is...
Is there anything new in the Drupal v6 of the book module that may allow me to do away with the 'wikibook' module concept and not have to re-copy/create a wikibook v6? I really would love to keep things as simple as possible.

An example of the situation:
mainRole - everyone in org is a member