DianeV

Typically, if your old server had cPanel, you’d go through cPanel to get to phpmyadmin, and then export (download) the database from there.

Then you’d import (upload) it through your current web hosting account.

Of course, there’s more detail to it than that, but that’s the general idea.

> I was able to backup the MYSQL database and all the files but I was not able to export any of the posts.

The posts are in the mysql database (along with comments, settings, etc.). If your new blog does not have any posts yet and it’s a WordPress blog, then you can probably use the mysql database on it. We’ll need more information, though.

It might help to contact the plugin author … you can probably find a link to his site in the Plugins section of your WP Dashboard.

> Do you know of a way to at least log back in?

No.

If you can access the database, then you can change the URL to the /wordpress folder there, but I’d be very cautious about that, because you can also mess up the database itself.

I’m thinking that that should have worked.

When you say “deleted a blog”, how exactly did you do that? If you can give more information, we might be of more help.

(Good for you for having backup copies of the files and the database.)

As esmi said, try resetting your permalinks, save, test site in browser, then set it back the way it was.

Oops. Looks like you fixed it. ??

It’s hard to give advice without knowing a lot more. Where were the 250 visits coming from … how were people finding or getting to your blog? Did something happen after that?

When you say you “deleted a page”, how exactly did you do that? Knowing would help us to give you good tips.

It seems like this would be in header.php … no?

This almost sounds like you have two headers, as most themes have only one — and if you’d linked to a page in the header file, then that would be applied to the entire site.

Otherwise, without more information, we’d just have to make guesses here.

Looks like you got it sorted out. ??

I doubt that you uploaded wordpress to your database, since those are two different things.

I am wondering whether the /web/content/ folders are an internal server path and so your site should really be accessible at ideometer.co.uk.

Have you tried https://www.ideometer.co.uk/wp-admin/install.php …?

—

Hm. I just tried that and got redirected to https://81.21.76.62/ideometer.co.uk/index.html. I would check with your web host to see what the issue is.

I’d start over. If your blog was originally at site.com/wordpress (or WordPress capitalized, for some reason), then that is where the 2.9.2 files should go — not in site.com/Wordpress/wordpress.

Delete the second wordpress folder (/Wordpress/wordpress), then open the wordpress folder on your computer and upload everything that’s in it (all the files and folders) into the WordPress directory … that is, don’t upload the /wordpress folder into /Wordpress so that you end up with /Wordpress/wordpress again.

Then try to run the upgrade.

WordPress does *not* have to be in the root directory, but there may be some confusion here.

– If you upload the wordpress folder (directory) to your root directory (whether root is called “www” or “public_html” or whatever on your server), then WP would not be in the root … it would be in the wordpress folder under the root directory:
site.com/wordpress/

– If you want WordPress to be in root, then after you extract WP from the .zip or .tar file, upload everything that’s in the wordpress folder to the root … but not the directory/folder itself. Then you’d access it as site.com.

That said, I’m not sure what’s causing the installation problem. There should *not* be weird lines of code at the top of each page during installation. I’m wondering if this has to do with how you uploaded the files.

I’m wondering whether your database is corrupted.

Whatever you do (and whatever is the answer), I’d back up the database immediately, if you haven’t done so already.