curious11

Hello again tomontoast,

No problem about the delay! The updated CSS you provided works great in Chrome now, thanks a bunch.

I tried out that new markup you provided for the header.php file. Unfortunately, it causes the same parse error, though on different lines. I’ll keep trying a bit later, I just wanted to give you an update.

Thanks again!

Ahoy,

Sorry, been a bit busy and didn’t get a chance to update this. Yep, I fixed it.

whooami, I appreciate the offer, but I wanted to try it out one more time. I used notepad++ this time to edit and it worked.

Thanks again for your help.

Thanks for your help, thus far.

I’ve inadvertantly caused another problem, thereby causing a headache and a desire to smash.

For the sake of my notebook, I’m going to let this sit for the night.

It just doesn’t make sense! I’ve edited the same index.php file, from the original, a variety of times, trying different things, etc. and still the chars?

I’ve used jedit as well and there are still hidden chars?!

I’m going to have another look at it and will take a look at the plugin files as well.

Visiting: https://www.domain.com

Yep, correct content shows up.

Visiting: https://domain.com

Shows the error and only the error on a blank white page.

Feel free to have a look here.

Excuse the mess.

I do realize the point your making. What’s frustrating for me is that I’ve tried the suggestions you and others have made to no avail.

Let me just iterate what the issue is, so that I’m sure we’re on the same page.

Problem:

Visiting: https://www.domain.com (works fine).
Visiting: https://domain.com (produces the error).

clearly then, you dont need the help of anyone with 4 years experience. best of luck.

? I don’t really understand how I offended you, but I do apologize.

Regardless, thanks for your time!

EDIT: I did try rewriting in notepad and saving again as per your suggestion, and it didn’t change the situation. This is why I said I don’t think that’s the issue.

I’ve also seen that page in the codex and tried it out. Unfortunately, it didn’t do the trick either.

Yep, right now it’s the following:

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

I did take care to edit in notepad and save as UTF-8, so I’m not sure that’s the issue.

Hello again!

I inserted that last bit of code and I got this error when trying to load the site:

Parse error: parse error, unexpected ‘}’, expecting ‘,’ or ‘;’ in /home/content/i/n/d/indecisiveian1/html/blog/wp-content/themes/isolated/header.php on line 74

You’ll have to forgive me, I’m fairly new at this and am learning as I go along. I have no clue what that means. My guess is that it’s a syntax sort of error? Anyway, you can see what’s happening, here.

Thanks again!

P.S. The current page CSS cod you provided earlier works in IE. I’m not sure what you’ll be browsing with, but it didn’t work in Chrome. Just letting you know in case you’re using Chrome or a similar browser.

Also, I reverted the menu code back to what it was so that you can view the page. The CSS you provided before is still incorporated though.

Hello tomontoast!

Thanks! I’ve tried out your solution. It works like a charm for all the page buttons. But, what I guess what I forgot to mention was that the first ‘button’ in the nav bar is relative to the posts portion of the blog. It’s the ‘home’ or default… ‘page’ for lack of a better word.

So, what happens when I’ve applied your solution is that when the site loads up, the ‘blog’ button (which refers to the posts area) is left looking unselected. However, when selecting the page buttons from that menu, the current selection displays as intended.

Conundrum!