Considering upgrading to WordPress 2.6

Are there any files within my WordPress 2.2 folder I should save to
use for the WordPress 2.6 installation such as
wp-config.php wp-login.php wp-admin/install.php ?

wp-config.php, just so you have the already working mysql connection settings.

If I ever wanted to re-install my old WordPress 2.2 blog backup file,
would it run on WordPress 2.6?

a mysqldump of the 2.2.x tables will not work out of the box in a 2.6.x install.

//

https://codex.www.ads-software.com/Upgrading_WordPress_Extended

I performed a mysqldump backup of my database.

OK, that’s the backup of your content.
You should also consider downloading/saving your custom theme files (if any), your uploaded (image) files etc. Just in case.

I am considering dropping the old blog files using MySQL

That doesn’t really make sense – there are no files in the MySQL. It “just” your all content (posts, Pages, comments) and settings for the blog.
If you meant you drop/delete the tables – then that’s OK, that will delete your existing blog from the DB.

———–
wp-config.php should be kept because you will need the info from it even if you want to replace it with a v.2.6.x file.
————-

If I ever wanted to re-install my old WordPress 2.2 blog backup file, would it run on WordPress 2.6?

Not out of the box. It will ask you to upgrade it.
Also, keep in mind that if you start a new blog, you will NOT be able to simply “re-install” the old sql backup file in it! With some work you can import the old posts but you need some workaround.

<wp-config.php should be kept because you will need the info from it even if you want to replace it with a v.2.6.x file.>

Perhaps, I can substitute my old WordPress 2.2 wp-config.php with the WordPress 2.6 to save on having to edit the WordPress 2.6.

But I there is https://codex.www.ads-software.com/Upgrading_WordPress_Extended

If there is not a SECRET_KEY define statement in your wp-config.php file, add one. Beginning with Version 2.5, a SECRET_KEY for salting (strengthening) user passwords was added to the wp-config.php file. To improve the chances your user passwords are not ‘hacked’ here’s an example of the line to add to your wp-config.php file:

(‘SECRET_KEY’, ‘RF63k93hb9shj3klvbn37sjd9a9n”‘); // Change this to a unique phrase.

I guess I should copy and paste data from my old WordPress 2.2 wp-config.php file into the WordPress 2.6 wp-config.php file.

Delete the old WordPress files on your site, but DO NOT DELETE
wp-config.php file;
wp-content folder; Special Exception: the wp-content/cache and the wp-content/plugins/widgets folders should be deleted.
wp-images folder;
wp-includes/languages/ folder–if you are using a language file do not delete that folder;
.htaccess file–if you have added custom rules to your .htaccess, do not delete it;
robots.txt file–if your blog lives in the root of your site (ie. the blog is the site) and you have created such a file, do not delete it.

In your Administration panel, under the Plugins choice, deactivate any Plugins. Because of the changes to WordPress, some Plugins may conflict with the upgrade process.

<If you meant you drop/delete the tables – then that’s OK, that will delete your existing blog from the DB.>

Yes, I meant to drop/delete the tables which would delete the contents.

Thank you for the https://codex.www.ads-software.com/Upgrading_WordPress_Extended link

and your replies to my post.

<Also, keep in mind that if you start a new blog, you will NOT be able to simply “re-install” the old sql backup file in it!>

If I wanted to keep my old blog and still setup the new blog

I found Installing Multiple Blogs at

https://codex.www.ads-software.com/Installing_Multiple_Blogs

You can do this whether you have the ability to create multiple databases or are limited to a single database.

I have a single database.

Single Database

As with the multiple databases solution described above, the wp-config.php file will vary for each installation. In this case, however, only a single line will be unique to each blog:

$table_prefix = ‘wp_’; // example: ‘wp_’ or ‘b2’ or ‘mylogin_’

As noted, you may use a prefix of your own making.

I guess I would only have to change the $table_prefix = ‘wp_’; to something else and this would create a separate set of tables within the single database.

Upload each wp-config.php file to its specific root/installation directory, and run the installation.

See Installing WordPress for more information.

https://codex.www.ads-software.com/Installing_WordPress