Upgrading Drupal

I have recently upgraded site to Drupal 4.7. After the upgrade I have noticed that the users with so-called "Site Administrator" roles do not seem to have the same permission levels as previously. After some investigation, I discovered there is no "User 1" at all so I dont' know how I can go about putting things right.

A number of issues have arisen because of this problem but I am sure that once I can figure out how to add a new "superuser" type user, I can proceed from there to fix things up.

I have flexinode working fine in a couple of sites created from scratch in Drupal 4.7

But I have failed miserably trying to upgrade from 4.6 to 4.7

I have put too many hours reading the long, very very long list of bugs and dozens of posts. I've tried to do things I understood ad things I didn't. No way.

Lucky me, I only had a flexinode event to upgrade, so I copied and pasted everything from my still alive 4.6 site, and I am clean.

But I have another site in 4.6 that relies heavily in flexinodes and copying and pasting is just out of question.

Of course, there are many things I'd like to do with that site that can't be done in 4.6, and I feel it is unfair to my clients to leave them stranded in the past.

So, if you have managed to succeed in upgrading with Flexinode, it would be great if you can post how you did it. It would be awesome if your tips were in plain English, too.

The amount of bugs and comments makes me think I am not alone. I am sure your help will be appreciated by the unwashed masses who can't write a decent line of code. Actually I wonder how many drupallers are dyed-in-the-wool programmers. I have the feeling that Drupal's phenomenal growth has a lot to do with the fact that it allows non-technical people produce work with a depth of functionality th

I've just upgraded my drupal site from 4.6.9 to 4.7.3.

first, i got lots of inoffensive little error messages from mysql like this one.

# /home/****/public_html/includes/database.mysql.inc on line 120.
# user warning: Unknown column 'vid' in 'where clause' query: SELECT * FROM ec_product WHERE vid = 227 in/home/****/public_html/includes/database.mysql.inc on line 120.

Always the same unknown column 'vid' in 'where clause' etc.

Well i dont know how to fix those ones so if you guys have an idea, please let me know.

Can anybody tell me where the "drupal_get_html_head()" function is being defined?

Drupal 4.7.3

thanks

I have been having a lot of issues with the 4.7.0 version of the categories module. when i pulled out the latest CVS version of it it complained about things missing from core. I figured it was time to upgrade to 4.7.3.

I am not sure what the upgrade path is - is there one???

This is what i did?

- copied over all of 4.7.3 OVER TOP of my 4.7.0 install
- replaced my settings file with oringal
- ran update.php (which reported it needed to update system module DB to 178

and that was about it:

after i was done:

My upgrade from 4.6 to 4.7.3 wasn't a piece of cake, but it worked mostly OK, with two problems that I can't solve on my own:

1. the user module and/or the profile module are giving me serious trouble.

• The user's list has vanished. I can't see it even when logging in as user 1
• Anonymous and authenticated users can't access user's profiles, although they have permissions to do so.
• Authenticated users with permission to change own username get a page not found message when trying to get their profiles.
• Visitors are allowed to create accounts, get their account detais by e-mail with a valid link, they can even go to user/xxx/edit and modify their profile, but user/xxx yields a "polite" (drupal formatted) not found page
• Only admins with permission to administer users can see the profiles

I read a posting about a similar bug and a subsequent issue but I get nothing clear out of them, except that this is an unsolved issue.

Lucky me, My 4.6 version of the site is still working fine. So this won't be a very very big issue

I am pretty sure that this problem has a lot to do with the upgrade, since I have two sites that were born in 4.7 and have no user.module problems at all.

What I don't know is if this issue is related to a recurrent error that is related to users, and has been documented but not explained -in my humble opinion- in several posts: