Upgrading Drupal

When updating from 6.1 to 6.2, I set to maintenance mode and delete all core files. During this few minutes time, if somebody is accessing my site, it will show "Warning..." and "Fatal Error...".

How to overcome this problem? It is because I totally delete core and install new core files and I don't want visitors to my website see the error message.

Once again, it was time to update (this time from 5.x to 6.x). I have my Fantastico auto-install my updates, so despite having changed the layout and files a small bit, I had always just clicked the update button and installed a new layout.

This time, that didn't happen.

The site http://www.artistsforumworkshop.org/_____/ has exploded, and I was hoping anyone had a suggestion? A few of the error messages (which make up the whole of the page) I shall give to you here, but do look at the actual page:

I've looked into this for awhile now and just cannot figure out what is going on.

I upgraded my site (http://www.humanjoe.com) from 5.2 to 6.x last week. Everything seemed to go fine but just yesterday I noticed that when a story, page, etc. is displayed the username is being left out of the submitted by tag at the end. The example below is copied from my site.

By at 04/21/2008 - 19:42 | Site | Read more

I just upgraded my drupal site from 5.x to 6.x, but I wanted to do a fresh install of 6.x so I made a new database. I would like to now move only my users and their blogs over from the old database into the new database. Can someone tell me all of the tables, etc that I need to copy and import into 6.x?

I made a mysqldump of a Drupal database running on mysql-server-3.23.58-4 and tried to restore it on a server with mysql-server-5.0.22-1.centos.1

I got the following error when importing the database:

[root@myserver]# mysql -u root -p mydatabase < mydatabase.sql
Enter password:
ERROR 1064 (42000) at line 200875: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'sql longtext,
countsql longtext,
changed int(11) default NULL,
PRIMARY KEY' at line 15

I had 5.2 running for a long time, and it worked great. If I logged in, I could read posts, submit comments, etc... the browser didnt lose my cookie, and drupal knew my session until I logged out.

After upgrading to 5.7, It seems that the login/session/cookie is not working properly...

I log in, and when I go to read a post, it doesnt show my the comments or menu, and instead looks as if I have not logged in at all. if I relogin, it still doesnt matter. This happens in FF2.0 and IE6. Both of which worked fine just fine with 5.2.

Any ideas?