Jeff F.

I’m sorry, I want to help but I don’t understand when you say you built the site did you do it from scratch or are you using a commercial theme or free one? You should be able to do it one of two ways unless for some reason your hosting does not allow sub domains, which I haven’t seen with any client.

You can set it up with the sub domain, and then yes you would set up a link on the main site to it so that would be blog.example.com.

Or depending on the theme you can set it up so the blog page displays your posts and it would be something like example.com/page just like any other page that links to the latest posts if the theme allows it. Hope that helps.

you may have to check out the actual support for that theme.

https://www.inkthemes.com/support/

But the page is loading a sidebar so is there a widget in there that is showing the pages? Look on the left of the Dashboard for Appearance>Widgets.

Xavier is referring to having something like blog.example.com when your main domain is example.com. Most hosting companies allow that at no extra charge and it must be done in the hosting accounts’s cpanel or similar configuration.

But you say that you have a website and a blog. Are you trying to move the blog to the website or is it already a page on the website and it’s not showing up?

You’re welcome. The other desktop browsers must have been recognizing it since it is a free font.

If I’m reading this right you’re calling the font as ‘font-family: jenna_sueregular;’
in your font face rule, but then font-family: JennaSue; in your css. They should match.

Sorry we’re getting a bit of delay with the response. ??

Did it work, I didn’t see the other question before I answered. Someone else with more experience might be able to weigh in, I’m just trying to give back a little and wouldn’t call myself expert.

But it just insures that the font gets loaded. The issue with Chrome was coming up where the fonts wouldn’t “appear” until you hovered over them. I would also consider putting the font in the root of your directory or even a “fonts” folder if you can.

PS I like your logo.

You bet, hope it works.

Oh I see, I was looking in the CSS in firebug. I normally load the fonts directly into the root directory.

But there was a problem a couple of months back with a Google Chrome update that sent a bunch of my sites a flutter until I found this bit of code through the forums. It’s stuck in there in the footer.php right before the <?php wp_footer(); ?> tag and the html and body tags. You would replace “Oswald” with “jenna_sueregular.”

<script>
jQuery(function() { jQuery(“body”).css(“font-family”, “Oswald”); });
</script>

Are you loading the font through the @font-face rule because I don’t see it in the css nor do I see that font uploaded in any folder

Have you checked with the hosting server? I encountered a similar error and it turned out the client’s hosting account was not supporting the most up to date version of php.

The index.php file is the one that controls the blog page. So what you want to do it take the code that makes your homepage the way you want it and call it something like homepage.php. And put back the original index.php file.

Then you can create a page called home that’s blank, choose the template Hompage (or whatever you name it) that is this homepage.php file and create a page called Blog that you then select as the posts page.

That’s the exact method I use all the time on sites that are child themes of twenty twelve.

If you want to check an example https://beinspiredblog.com

Do you have the right command and file location

<link rel=”shortcut icon” href=”<?php echo get_stylesheet_directory_uri(); ?>/favicon.ico” />

@sleneau

Thank you so much for your help. I was not familiar with this and I”m looking into your link for help on older browsers. I really appreciate your time.

Mike, thanks I think that might be what they’re looking for but they had to take the dev site down so I don’t know when I’m going to back at it but wanted to thank you for the response.

I had to choose another gallery. There’s no place to mark this resolved now.