[livewellplayhard]

OK, thanks. I'll give it a try!

Jennifer

[livewellplayhard]

Hi Davinder. Thanks for your response!

Within which section of the css should I change this?

Rather than changing the #widgettitle h4 font size to be the same size as h1, could I change the #widgettitle for my Blog page to be h1?

Thanks,
Jennifer

[livewellplayhard]

THANK YOU!!

That was it. I vaguely recall doing this back in 2012 when I originally set this site up, then left it for two years.

Big sigh! 🙂 I really appreciate your help.

[livewellplayhard]

Hi - I'm not sure I understand. Each category has its slug - what am I comparing this to?

[livewellplayhard]

Hi anitac. I do think you're right that there is some confusion.

I tried what you suggested: set the Permalink setting back to the default. My pages then went into redirect loops and wouldn't load at all. I set it back to /%category%/%postname%/ - and the pages loaded again, however, I still have the same issues:

- the orphan Livelihood category remains on the Blog page with no posts underneath.
- the two "your-calling-and-livelihood" posts appear under the page of the same category name, but will not display on the Blog page.

I also deleted all tags, categories containing "livelihood" and the lone Livelihood heading remained.

What I did notice is in Firebug is this. On the Blog page:

Relationships Category (which does work and display its posts on Blog page) contains this code:
<h4 class="widget-title widgettitle">Relationships</h4>
<div class="post-463 post type-post status-publish format-standard hentry category-social entry">

Mind, Body & Spirit Category (which also works and displays its posts on Blog page) contains this code:
<h4 class="widget-title widgettitle">Mind, Body & Spirit</h4>
<div class="post-164 post type-post status-publish format-standard hentry category-mind-body-spirit entry">

Livelihood on the Blog page only contains this:
<h4 class="widget-title widgettitle">Livelihood</h4> it is not followed by the same <div>

???

[livewellplayhard]

Hi Summer,

Yes, any feedback helps. I believe I've gotten that behavior fixed. Thanks so much for your help as well.

I'm now having issues on with the Blog Template page in its own support post: Posts for Certain Category Don't Appear on Blog (but other categories do).

Working through this, one item at a time. 🙂

Jennifer

[livewellplayhard]

Fixed. Brute forced somewhat, I think, but fixed. Thanks for the help, Summer. I was able to learn from your suggestions.

I'm an ex-web developer, but I've been out of it for a long time. 🙂

Thanks again,
Jennifer

[livewellplayhard]

Thanks Summer,

Good point about clearing the cache, which I did for both Chrome and Safari. I also restarted (it was time anyway) and now this is getting really weird.

In Chrome :
- Nav & Content links: Charcoal/Charcoal (unvisited/visited) - this is similar to original Lifestyle theme color options (which were still there this morning). The Content links are in fact specified in the css as Light Blue (#509ac9), but appears as Charcoal in this browser.
- Blogroll links: Bright Blue/Charcoal (new, not desired!)

In Safari:
- Nav & Blogroll: Bright Blue/Charcoal (new, not desired at all)
- Content links: Light Blue (desired)/Charcoal - this combination is desired.

This is what is desired:
Primary & Secondary Nav: Charcoal/Charcoal
Content: Light Blue/Charcoal
Blogroll: Charcoal/Charcoal

BTW: The ability to configure Color Options in Genesis disappeared this afternoon - Genesis 2.02 upgrade perhaps? - and started me down this rabbit hole... 🙁

[livewellplayhard]

Thanks, Summer.

I believe that's the code that I added (I think)

The original code is commented above:

/*
.entry-content a,
.entry-content a:visited {
text-decoration: underline;
}
*/

But if you look on the About page, where there are some links in the content, they still appear as black.

I wonder if there's something that's overriding that. I saw in Firebug that perhaps the <p> attributes might be inherited here?

Jennifer

[livewellplayhard]

Thanks, again. I finally went in and started to hack the .css, which eventually worked but I lost several hours.

I also don't see an option to rollback to the previous version. I have also searched and searched for how to do this - would you mind sharing this as well? Then I promise I will leave you alone 🙂

I did turn auto-update off for Genesis though, which I suspect might have played a part in "now it's there, now it's not".

[livewellplayhard]

Thank you so much, Andrea! Nice job.

Jennifer

[Author]

Posts