Upgrading Drupal

Hello all,

I started with Beta6 in which I added content. Then I installed RC2. (seperate install). I have only done some minor page.tpl.php and style.css changes in my Beta6 install bluemarine theme.

I have two questions:

1) Are there differences in database between Beta6 and RC2? Can I use the Beta6 DB (so as to recycle already entered content) with the RC2 files without issues by just pointing the settings.php to use the beta6 DB? Or do I manually have to transfer all content from Beta6 to RC2?

**** I posting an upgrade issue here, discussed in http://drupal.org/node/56107. This problem is also happening with upgrading to 4.6.5 and hence I am escaling it to a new post and it has new details also ****

Folks,

I need to move computer, convert and upgrade from 4.6.4 runing under MySQL3 to another computer Apache 2.2 and MySQL5 with 4.7. I am willing to reconfigure the system, I just want to move the actual data.

The best way I can think of is to export the taxonomy, the users and the nodes. I don't care about the rest.

Which MySQL tables should I export/import?

	blocks                  10          Do I really need this, I can retype it
	book                    253 
	comments             0
	node                    254 	
	term_data            16          Do I really need this, I can retype it
	term_hierarchy     16          Do I really need this, I can retype it
	term_node            249 	
	url_alias               254 	
	users                    3          Do I really need this, I can retype it
	users_roles           4          Do I really need this, I can retype it
	variable               169       What's that?
	vocabulary            4           Do I really need this, I can retype it
	vocabulary_node_types 	 13 	Do I really need this, I can retype it

Is there something else that I should get?

Thanks

I don't much like having error reporting set to anything but E_ALL, but the latest changes to bootstrap.inc produce notices in the conf_init() function. (Line 146 checks for isset($part[('path']) before using it, but line 148 does not.)

So you may need to change your code, or change your error reporting to E_ALL ^ E_NOTICE if you get warnings there.

Fortunately I'm doing this on a test site...'cause it's scary.

Since i tried to update, scratch the site and start over in 4.7 all the drupal urls point to site.com/cgi-bin/whatever...

The cgi-bin cannot be found anywhere and i didn't modify the site's variables... Only happens in 4.7.

As a result all updates, installations, etc fail...

I tried the clean urls fix via phpmyadmin (as the apply buttons try to go to cgi-bin and dont work) but that didn't work either...

I searched EVERYWHERE for the darn cgi-bin string in the files and php and couldn't find it...