tonybemidji

Just a follow-up… This may be a Multi-Site issue. After confirming that Font Awesome was installed and otherwise working I commented out the lines in menu-image.php that check for “font-awesome/index.php” in the options table. Since this is a multi site setup there are several different options tables.

Works fine now.

Another clue… this is the start of this particular <style> section:

<style type="text/css">PICK AN ELEMENT NOW - or type CSS selector(advanced) {
font-size: 30px !important;
color:  !important;
}
DIV DIV DIV.advanced_wp_columns_wrapper.null DIV.advanced_wp_column.null SPAN, DIV DIV SPAN.ui-draggable STRONG SPAN.fontplugin_fontid_1408_DroidSans.ui-draggable {
color: #ffffff !important;
font-size: 23px !important;
}

Any idea what might be inserting this into the header?

Thanks… tried that. If you inspect the Title in Chrome you can see that change is there, but is subordinate to another entry that takes precedence. Trying to figure out where the heck that is set!

Ah… Occam’s razor again. Just removed the Ditty plugin folder and all is well.

Resolved!

Finally figured it out.

I forgot to change the AllowOverride parameter for /var/www/html on the Centos system. Made that change and everything is looking good.

Thanks for the help bernbe01 … It was a good reminder to make the permissions changes, etc.

Thanks for the reply bernbe01…

I am able to get to wp-login. I renamed the existing .htaccess to .htaccesstemp and then went to the Permalinks settings and saved. I get the message that the permalink structure has been updated, but the .htaccess file is not created in /var/www/html on the Centos system. I even changed permissions on that directory to 777 just to be sure I could write to it.

I feel like I’m missing something pretty basic here.

This is the WordPress section of the functioning production .htaccess file:

# BEGIN WordPress
<ifModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
</ifModule>
# END WordPress

I think I finally have it. I just created a backup install of my site and replicated the database to test this out.

My main problem was the .htaccess file. For a new (3.5+) Multi-site/subfolder install it should be:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Then I used the Search and Replace (2.65) plugin and did a search and replace on just the “content” and “meta” for each site.

There were a couple of other menu related items that just had to do with caching, but I think for the most part I can replicate this on the live site.

Thanks for the help!

I’ll make the base changes again and double-check.

Is there something specific that I should be looking for in the wp_x_posts tables? I’m not seeing anything other than the GUID field that contains a reference to the old domain name.

Thanks Mike…

I changed everything back for now, but here is basically what I observed:

I have a page right now called Administration. The URL: https://wptemp.bemidji.k12.mn.us/district/administration/ works. When I make the above changes, going to https://www.bemidji.k12.mn.us gets me to the home page just fine. But if I hit the link to Administration it goes to https://www.bemidji.k12.mn.us/district/administration/ and gives me the 404.

This is the root blog, so looking at wp_posts I see an entry for Administration but the only place I see a reference to the old “wptemp” is in the GUID field… which is supposedly not to be touched.

OK… I’m still puzzled.

I’ve gotten beyond database errors, that was a stupid mistake on my part.

again… no files moving… just changing from “wptemp” to “www” in the domain.

I have done the following:

Change wp-config… define(‘DOMAIN_CURRENT_SITE’, ‘www.bemidji.k12.mn.us’);

Then, in the database I changed all instances of “wptemp.bemidji.k12.mn.us” to “www.bemidji.k12.mn.us” in the following:

wp_options: site_url, home
wp_blogs: domain for the site
wp_site: domain
wp_sitemeta: siteurl

So I can get to the admin dashboard now using “www.bemidji.k12.mn.us/wp-admin” and the home page shows up correctly at www, but now if I click on any link to get to a page I get a 404 error. The instructions say not to mess with GUID data and that is the only place I see the old URL in the wp_posts table.

I have also changed the corresponding data for each sub-site and now when I try to go to “www.bemidji.k12.mn.us/central/” I just get bumped back to the main home page.

What am I missing?

Nice… Disabled all but three plugins that I have used since I created the blog. Found out it was one of the three.

Thanks for the suggestion. Problem solved.

OK… More info. This seems to be (somewhat) related to the images in the post. If I get rid of the anchor tags around a photo in my top post, then clicking the “See the rest of…” link just takes me right back to the home page. However… just a bit further down in the “Walleye Fishing Week in Review” post, if I click the “See the rest of…” link under that I go to a page that displays the next photo below the break.

I really have no unusual html in these posts. I’ve disabled all but a few basic plugins (this was working once upon a time!).

Tough to troubleshoot the html since it really isn’t messing up the layout… it’s just taking me to a page to which one would not expect to be taken.

I’ve tested this with the default WordPress theme and get the same behavior… so I assume this rules out the theme.