Upgrading Drupal

I believe Flexinode's upgrade to 4.7 has been very badly handled. Note that I am not criticising flexinode developers per se, but questioning the decision to more or less abandon development in favour of CCK, which is not yet fully functional, leaving hundreds of users between the devil and the deep sea as far as upgrade to 4.7 is concerned.

upgrading a 4.6.8 site to 4.7.2. it's gone mostly ok; a few stray problems with the odd database (i really really hate the Quotes module at this point).

but when i create a new node, it's being numbered beginning at 0. i tried running a bit of sql i found in here to reset totalcount, but that did not work. i cannot find anything else, either in the db or the forum.

help please?

Hi Everybody

i was configuring Quiz module in my application.it configured correctly but whenever i was trying to create Quiz following error generated.

anybody can help me why this error is?

I want to do an upgrade from drupal-4.6.4 to drupal-4.6.8
in the upgrade documentation, it says this:
"Remove all the old Drupal files then unpack the new Drupal
files into the directory that you run Drupal from."

does that mean I should move the entire Drupal-4.6.4 tree aside and unpack the new Drupal-4.6.8?
aren't there modules that should be kept rather than reinstalling them?
I also have a custom theme which I assume I can copy into the new theme directory.

thanks for any tips.
Susan

i got this warning box prior to the list of run queries for the update of 4.7.2.

user warning: Duplicate key name 'vid' query: ALTER TABLE
node ADD UNIQUE (vid)
in /var/xxxxxxx/drupal/includes/database.mysql.inc on line 120.

the update completed with only the following failure (see 3rd)

Update #180

After upgrading to 4.7 all my OLD links which had a relative path are broken now.

All the OLD links look like
mysite.com/node/node/1234 or mysite.com/admin/node/1234
instead of
mysite.com/node/1234

the link url is href=node/1234

This does't happen with new posts, where links are fine and url are href=/node/1234

I guess this is a .htaccess problem, any ideas?

regards