“Visit Site” button takes me to site home page

Any chance your Blog Address (URL) is https://www.site.com instead of https://www.site.com/wordpress?

Administration > Settings > General

Oh, if you are at 2.7, deactivate and delete the WordPress Automatic Upgrade Plugin–you don’t need it and will likely cause you future problems.

Thanks MichaelH

A) Nope. It is set to https://www.site.com/wordpress.

B) I installed WP Automatic Update to my original ver 2.2. Since then I’ve erased the wordpress dir via ftp, via my web provider’s interface, reinstalled 2.2, reinstalled 2.7… All flavors of all that I can think to do.

It “feels” like everything is there (posts in databeast) but I can only “see” things through the admin interface. No one can visit my real blog. (And the world is much worse off not enjoying my witty prose…)

Then link to the site please.

“Any chance your Blog Address (URL) is https://www.site.com instead of https://www.site.com/wordpress?”

Just for grins I changed to https://www.site.com/temp, saved, and changed it back.

No dice.

It feels like I am 99.99% there and just missing one little key…

ETA: Link to site: https://www.circuitgizmos.com

So visiting https://www.circuitgizmos.com/wordpress should show the blog?

So your wordpress/index.php file should be something like:

<?php
/**
 * Front to the WordPress application. This file doesn't do anything, but loads
 * wp-blog-header.php which does and tells WordPress to load the theme.
 *
 * @package WordPress
 */

/**
 * Tells WordPress to load the WordPress theme and output it.
 *
 * @var bool
 */
define('WP_USE_THEMES', true);

/** Loads the WordPress Environment and Template */
require('./wp-blog-header.php');
?>

And there should be NO index.html in the wordpress folder.

If that doesn’t solve the problem, look for problem in .htaccess.

“So visiting https://www.circuitgizmos.com/wordpress should show the blog?”
Yes.

“So your wordpress/index.php file should be something like:”
Yes. No change from the 2.7 zip file.

“And there should be NO index.html in the wordpress folder.”
There is not.

“If that doesn’t solve the problem, look for problem in .htaccess.”

My what what? (And where?)

ETA: I see it now.

It says:

ForceNoProxy On

Have no clue what the .htaccess thing does ?? Where’s whooami when we need her – she’s the .htaccess expert???

This is weird, but saw it on some other thread….delete the index.php in the wordpress folder. Visit https://www.circuitgizmos.com/wordpress and you should get an error of some kind, then put the index.php back.

[edit off to sleep for me]

Tried. Twice. I didn’t see an error, but got a directory listing instead. Put index.php back and still got only my root page.

When I had 2.2 installed, the blog was in https://www.circuitgizmos.com/wordpress where I expected. Well it was visible visiting there both directly and through the “view” link in the admin tool.

Baffling.

Sorry – I’m baffled too.

When you wake up and visit this thread – Thanks for helping.

I’ll bear your first born (which apparently men can do now – ick) if you have a dream where the solution is presented to you in large burning letters.

Extra kid if you remember it when you wake up.

??

One thing I could come up with is either a theme or a plugin doing something. Change to the WordPress Default Theme and deactivate all plugins.

Then there’s the ugly thought something weird happened in the 2.2 to 2.7 upgrade. That process should work, but success has been had by others by upgrading from 2.2 to 2.3, to 2.5, to 2.7. Ugly ugly…

No thanks on that generous offer, regardless of the outcome of this thread!

No thanks on that generous offer, regardless of the outcome of this thread!

You are most wise.

One thing I could come up with is either a theme or a plugin doing something. Change to the WordPress Default Theme and deactivate all plugins.

Zero plug-ins, zero themes (other than default). I don’t have posts in my database (other than the default Hello World).

Then there’s the ugly thought something weird happened in the 2.2 to 2.7 upgrade.

If I uninstall everything, clear directories, and just install 2.7 I have the same issue. If I just install 2.6.5 I have the same issue. If I install 2.2 and install 2.6.5 or 2.7 “over” 2.2 I have the same issue. My only hand-edited file is wp-config-sample.php with the site-specific info added to it and saved as wp-config.php. I used the 2.2 version of that file saved to my local hard drive as a source for the specific info (which also matched the info my web provider, uh, provided) and used a text editor to copy/paste.

I can only conclude that the screw up was out of my hands.

That process should work, but success has been had by others by upgrading from 2.2 to 2.3, to 2.5, to 2.7. Ugly ugly…

Yes, that is ugly, but it might be one of the few options that I have left to me.

What are the revisions? I start at 2.2. I know of 2.6.5. Should I do all of the minor/minor revisions as well?

*sigh*

Well if you did a fresh install of 2.7 then the upgrade process really can’t be the issue.

Wonder if your host would have any input?