Post installation

How do I assign Admin rights to another user?

I have some problems when setting the path in the menu function for my module.

Every thing goes fine is I did this:

if (!$may_cache) {
            $items[] = array('path' => 'xxx/yyy/' .$m_id, 'title' =>..... 
}

or
$items[] = array('path' => 'xxx/' .$m_id .'/yyy', 'title' =>....

But when I tried this:
$items[] = array('path' => 'xxx/yyy/' .$m_id .'/zzz', 'title' => ....

I have a problem. When accessing a site at http://www.site.com, users can log in and do whatever their roles allow. However, when users go back and access the site through http://site.com (without the www), their login resets or does not appear logged in. They have to re-login in order to see that page.

I'm thinking this is a problem with:

1. .htaccess file
2. Cookies -- the way login information is being stored

Help!

Hi,

I just want to create a new menu and the following warning showed up:

user error: Access denied for user: 'XXX' to database 'XXXX'
query: LOCK TABLES sequences WRITE in /srv/www/XXX/XXX/html/XXX/includes/database.mysql.inc on line 66.

warning: Cannot modify header information - headers already sent by (output started at /srv/www/htdocs/XXX/html/XXX/includes/common.inc:384) in /srv/www/htdocs/XXX/html/XXX/includes/common.inc on line 192.

XXX is my user name etc. ;)

What does this user error mean???

THX for answers

Greetings

I cannot figure out what the image reference block in 4.7 is supposed to do. I thought it would be like the book navigation block and display some additional choices for images, but nothing is displayed even when I am in the galleries or for individual images.

Can anyone explain what this block is for?

I have a newly installed 4.7 implementation with an odd problem: every time I update a site feature in the admin area, drupal returns a blank screen. I can use the browser's back button to return to the function, then navigate to the next thing, but that's sort of weird. The function that returns the blank screen will invariably have worked, so it's as if some generic "updates accepted" module is failing.