Sean Davis

Now we’re talking!

1. I couldn’t really wrap my head around that one. Can you explain it in more detail? Any examples out there exist already? I think I may be missing the context.

2. Not a bad idea at all. I agree that this plugin is already a post grouping but it most certainly doesn’t hurt to append related posts from the blog to the course box. Just because it’s not part of the course doesn’t mean it’s not relevant. Good idea!

3. I’ve already got this one on my dry erase board. ??

Thanks for the feedback!

I’m glad you like it, Chris! Be sure and let me know if you’d like to see more functionality added to either the core or through an add-on. I’ll be extended SCC in multiple directions in the future!

The hyphen property is pretty new and browser support is shaky from one to the next. It looks like normalize.css file has -moz-hyphens: auto; on all paragraphs. Let’s override that.

Put this in whatever stylesheet you’re set up to edit:

p { -moz-hyphens: none; }

Clear your cache after that’s saved. Let me know.

Something (or someone) has added a <style> tag to the bottom of this post in some fashion and it’s packed with CSS. https://thecrucialvoice.com/2014/04/08/answers-lie-in-the-truth/

They attempted to comment out the CSS but they did so with HTML comment syntax… <!-- ... -->. They wrapped the CSS in that sort of comment when they should have wrapped the entire <style> tag with it. Inside of the style tags, the HTML is irrelevant. That’s CSS territory. So move the HTML ends outside of the opening and closing style tags.

Until that’s done, any page of your site, including the blog home, that displays that post will adopt that CSS and turn the links blue and purple, as the improperly commented CSS suggests.

Are you using the Customizer or are you writing CSS? Can you post a link to your site?

Can you post a link to your site so we can view the CSS?

No problem!

It happens! Text editor syntax highlighters will catch those kinds of little inconsistencies for you. I’m glad that resolved the issue!

It’s just my cropped screenshot. I could see the full site.

The single quotes in your get_header() function look funky.

<?php get_header(‘custom’); ?>

Copy this instead.

<?php get_header('custom'); ?>

That might do the trick.

The blog listing uses the index.php template in the root of the theme. That’s what you’ll want to edit. In there now is an empty the_content() function. Use these examples from the Codex to customize it to your liking. Then any time you use the regular `<!–more–> tag in your content, it’ll read the customizations you made to that function.

What exactly should we be looking for (or not seeing)? All themes are different so it’s tough to guess. Here’s what I see. That image is the background of the site’s header element. If that’s not the image you’re speaking of, post a few more details and I’m sure we can figure it out.

I can’t see the actual code you used so it’s hard to say if you used it correctly or not. But if you have just one div that only logged out users need to see, you should use:

<?php if ( ! is_user_logged_in() ) { ?>
…put your div here…
<?php } ?>

https://codex.www.ads-software.com/Function_Reference/is_user_logged_in

To protect your edits from future Suits theme updates, all you have to do is create a child theme.

With that set up and activated, copy the Suits theme’s footer.php file into the root of your new child theme. Then you can edit that file as you’d like. Any other changes you need to make in your theme, you’d continue to work inside of your child theme.

Haha I do that a lot too. Sometimes I just have to wipe it all clean and start from scratch again. Glad it’s working! ??