Fresh installation

Why not just allow WordPress to take over the root domain?

Esmi,
thanks for the input. I had thought of this, but then when people visit our website they will see https://www.example.com/wp/whatever correct? I want them to only see https://www.example.com.

Also I kind of like the idea of a fresh install of wordpress.

then when people visit our website they will see https://www.example.com/wp/whatever correct?

No – they will see https://www.example.com/

The only time they’ll see https://www.example.com/wp/whatever is when they view Posts (as opposed to Pages). The only other option would to physically move the new site using the relevant instructions in Moving_WordPress – which is far more complex.

Thanks for the input. I think the best bet is to do as you suggested and allow WP to take over the root domain. One final question. Am I correct in assuming that if I do this that the url for the RSS feed that is currently used for iTunes Podcasting won’t change?

Esmi,

I followed the instructions but got a white screen of death. I can still log onto WP administration, but when I go to my root directory it’s just a blank white screen.

The only thing that wasn’t clear in the instructions was if there was not .htaccess file in the wp directory to copy over to the root. I do have an .htaccess in my root already, so after googling for a solution I added some WordPress specific code to the existing htaccess file. Here are the contents of the file

'# -FrontPage-

# BEGIN WordPress

<IfModule mod_rewrite.c>
ErrorDocument 404 /index.php?error=404
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName upperroomcf.org
AuthUserFile /var/www/vhosts/upperroomcf.org/httpdocs/_vti_pvt/service.pwd
AuthGroupFile /var/www/vhosts/upperroomcf.org/httpdocs/_vti_pvt/service.grp

Options +FollowSymlinks
RewriteEngine on
RewriteBase /
#//RewriteRule ^https://upperroomcf.org/Media/pictures.shtml https://upperroomcf.org/ [L,R=301]
#//RewriteCond %{HTTP_HOST} ^(www\.)?upperroomcf\.org$ [NC]
#//RewriteRule ^ https://wp.upperroomcf.org [R,L]

RewriteCond %{HTTP_HOST} ^www\.wp.upperroomcf\.org$ [NC]
RewriteRule ^(.*)$ https://wp.upperroomcf.org/$1 [L,R=301]

#//if not already blog.website.com
#//RewriteCond %{HTTP_HOST} !^wp\.upperroomcf\.org$ [NC]
#//if request is for blog/, go to blog.website.com
#//RewriteRule ^wp/$ https://wp.upperroomcf.org [L,NC,R=301] 

#//301 Redirect Old File
#//Redirect 301 /Media/pictures.shtml https://www.upperroomcf.org'

The Rewrites could probably be deleted they are experiments I was doing, but the stuff between End WordPress and Options +FollowSymlinks I’m not sure about.

My index.php which I COPIED to the root (per the instructions) looks like this

<?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( dirname( __FILE__ ) . ‘/wp/wp-blog-header.php' );

I did change my theme after doing this. Perhaps this is the issue.

Ok now I’m really confused!!! If I go to https://upperroomcf.org/wp the blank theme pops up.

What did I miss????

Thanks in advance!

Try checking your site’s error logs for messages. Your hosts should be able to help you accessing your site’s error logs.

There are errors in the error log but most of them refer to a robots.txt file not being found. I only found one wp error

[Tue Jan 28 23:50:21 2014] [error] script '/var/www/vhosts/upperroomcf.org/httpdocs/wp-login.php' not found or unable to stat
[Wed Jan 29 01:56:57 2014] [error] File does not exist: /var/www/vhosts/upperroomcf.org/httpdocs/robots.txt
[Wed Jan 29 04:43:53 2014] [error]  File does not exist: /var/www/vhosts/upperroomcf.org/httpdocs/wp/wp-content/themes/OptimizePress

I don’t see what these have to do with the white screen of death.

Steps I have taken:
1. change Site URL to https://www.upperroomcf.org — I didn’t get an error like the codex said
2. Copied index.php and .htaccess from https://www.upperroomcf.org/wp to root
a. there was no .htaccess file in the wp directory, but there was
one in the root so I added some wordpress specific code to that
one
3. Made a backup and then deleted the index.html file in the root. there are other html files but they have unique names
4. Made sure the copied index.php was edited to

/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . ‘/wp/wp-blog-header.php' );

adding the wp directory
5. logged back into my site, and it worked. I had default permalinks set so no adjustment was needed.
6. Uploaded a new theme
7. Tried https://www.upperroomcf.org
8. White screen of death

What have I missed?

Well… I figured it out. Some how when I downloaded the index.php file to add the wp textedit changed the first ‘ to a strange character. This only showed up when I edited the file through control panel’s file manager.

So simple… and irritating!!!