You would lose all your custom plugins and themes. Also the upgrade is NOT about having new files (or, only partially) – it is about changing the database structure.
Why do you want to reinvent the wheel?
2 days ago moshu wrote:
> You would lose all your custom plugins and themes.
not a problem–especially since there can be compatibility issues. i’d rather add these things manually.
.
.
.
> Also the upgrade is NOT about having new files (or,
> only partially) – it is about changing the database
> structure.
right, but WP will detect the old database structure and convert it–i don’t need to do an in situ upgrade for that to happen.
.
.
.
> Why do you want to reinvent the wheel?
sometimes i modify fundamental WP files and don’t feel integrating said changes with a new WP release.
.
.
.
so, for clarity, there is no configuration information stored outside of the database, correct?
right, but WP will detect the old database structure and convert it–i don’t need to do an in situ upgrade for that to happen.
I have no idea what are you calling “convert”. WP will ask you to do an upgrade. How is that different than the normal upgrade process?
2 days ago, moshu wrote:
>> right, but WP will detect the old database
>> structure and convert it–i don’t need to do
>> an in situ upgrade for that to happen.
>
> I have no idea what are you calling “convert”.
> WP will ask you to do an upgrade. How is that
> different than the normal upgrade process?
i meant upgrade when i wrote convert.
2 days ago, besonen wrote:
> so, for clarity, there is no
> configuration information stored
> outside of the database, correct?
what configuration information is stored outside of the database?
You are on the forum for one year. You should know by now that nothing is stored in files in WP, except your wp-config.php file.
I tried to follow the upgrade instructions. I first backed up my old installation to my local hard drive. Then I deleted everything as instructed on my web server /blogs directory:
Delete your old WP files, saving ones you’ve modified.
Then I copied all the new files over to the /blogs directory. After copying over my own wp-config.php file, I get the 5 minute install screen when I try to open my blog. If I try to run the wp-admin/upgrade.php, it just opens it my text-editing program. I don’t know if I should run the 5-minute install or not? My database is OK; I did a dump on that and it looks good.
But now my blog is not accessible and I don’t know if I should reinstall it. Will I lose all my data in mysql?
UPDATE: OK, I remembered when I first installed WP, I had given my database a temporary name. Then, as I was configuring it, I changed that name to more accurately reflect what my blog is all about, not realizing that the first name would still be there.
Once I changed to the correct db name in the config file, all is well!
But I have to admit I’m still a little nervous about the actual upgrade as WP says my database is up-to-date and does not require an upgrade (when I run /wp-admin/upgrade.php)
If you try to “re-install” it – then YES, you will lose everything.
EDIT. Upgrade from what to what?
Oops, sorry for not providing that information.
I had version 2.3 and was upgrading to 2.3.1
BTW, thanks for your help!
You don’t even have to run the upgrade.php from 2.3 to 2.3.1
And next time start your own thread, don’t hijack something that is NOT related to your questions…
OK, I’m sorry. I have never used this kind of support system before so did not know I was breaking the rules…
