Tim Nicholson

I’ve definitely never seen that error message. I’ve been using WordPress v4.4.2 since its been out. I’m sure its an issue with a plugin as there is no code anything like that in my themes. I’d be happy to help you debug it, though, if you want to post back here.

Yeah, there is quite a bit of complex media queries involved to get that fixed navbar at the top. The WordPress admin bar complicates it even more. But the padding you are talking about is all adjusted in Spot’s style.css right at the top. It starts with basic “body” padding, then adjusts it to two different sizes of the WordPress admin bar, depending on the screen width.

I see you’ve switched the site to a different theme that doesn’t have a transparent navbar, but used javascript to adjust the navbar height as you scroll down the page. This is a very popular style right now and it’s high on my priority list for a new child theme to Flat Bootstrap.

I’ve actually got that working in a child theme I’ve been playing with, but it’s one thing to handle a single website and another to try to address all the possible different usage scenarios. Specifically, how should a transparent navbar react to a user not having an image header on a particular page? There is just a lot of logic to think through. If you email me, I’d be happy to send you my code. I just don’t want to post it on github and have someone think its a completed theme ready to use.

I’d probably do that with CSS. Inspect the styles on the specific page you are talking about. There should be unique identifier for it. Then use that identifier to do something like this:
.<identifier> .section-image-overlay { display: none; }

The identifier will probably look something like page-id-407.

Yes, displaying the_content() instead of the_excerpt() will display whatever is in the post including any images. For the blog index pages where you only want to display the_excerpt you’ll need to find a function somewhere in another theme that retrieves the first image in the post and uses that when a featured image isn’t added. There are many themes that do that, but the reason I don’t is because nowadays people add a lot of “icons” their posts such as social media icons, profile pic thumbnails, even emoticons, etc. It would be hard to determine which is the first “real” image that you would want as a featured image.

To get you started, you would take something like this from the theme:

<?php if ( !is_singular() ) : ?>
		<?php if ( has_post_thumbnail() AND !is_search() ) : ?>
			<div class="post-thumbnail">
				<a href="<?php the_permalink(); ?>" title="<?php the_title(); ?>">

				<?php the_post_thumbnail( 'post-thumbnail' , $attr = array( 'class'=>'thumbnail img-responsive post-thumbnail' ) ); ?>
				</a>
			</div><!-- .post-thumnail -->
		<?php endif; ?>

And extent it to something like this. But you’d need to add a function to functions.php called something like get_the_first_image(). In that function you can add the CSS classes “post-thumbnail thumbnail img-responsive” or you could pass those in as arguments like the_post_thumbnail() does. These classes are needed to style the image.

<?php if ( !is_singular() ) : ?>
		<?php if ( has_post_thumbnail() AND !is_search() ) : ?>
			<div class="post-thumbnail">
				<a href="<?php the_permalink(); ?>" title="<?php the_title(); ?>">
				<?php the_post_thumbnail( 'post-thumbnail' , $attr = array( 'class'=>'thumbnail img-responsive post-thumbnail' ) ); ?>
				</a>
			</div><!-- .post-thumnail -->
		<?php elseif ( get_the_first_image() ) : ?>
			<div class="post-thumbnail">
				<a href="<?php the_permalink(); ?>" title="<?php the_title(); ?>">
				<?php echo get_the_first_image(); ?>
				</a>
		<?php endif; ?>

Yes, you can remove those filters. lisajwells advice is good. The specific filters you would want to remove are xsbf_add_container and xsbf_end_container.

What I’m doing is trapping plugins that produce “after content”, such as social sharing icons, and moving them down to the bottom of the page. In v1.8 I got a little too aggressive with that. I quickly release v1.8.1 to set it back to what it was. Just today I released a major code update with v1.9 and think I have the problem solved for good. Let me know!

Thanks for the kind words! Do you mind if use this as a testimonial on my site? I can leave out any personal information other than your first name if you are concerned about that.

This is standard Bootstrap functionality, in which this theme is based. I’ve not seen or heard any issues with the top navbar not collapsing. It looks like your site is working just fine now. I see you did a lot of CSS customizations to give it a unique look and feel, which is great.

This is a Jetpack feature. I haven’t actually incorporated it into a theme yet. But Jetpack itself should allow you to crop the image and display is as the “favicon” on your site.

That’s easy to do with a custom menu. Add whatever pages you want (you may have done that already). Then open up the dropdown on the menu item you want to change and change the title to whatever you want. In this case, change it from the default which is the page name (“BowWow Meow Pet Boutique”) to simply say “Home”.

I would change it with a site-wide CSS plugin, such as comes with the Jetpack plugin. It’s easy to do with CSS.

My code is like this:

body {
	font-family: Arial, Helvetica, sans-serif;
    font-weight: 300;
    font-size: 18px;
    color: #555;
}

h1,
h2,
h3,
h4,
h5,
h6 {
	font-family: Arial, Helvetica, sans-serif;
}

It sounds like you want this:

body {
	font-family: "Lato", "Helvetica Neue", Arial, sans-serif;
    font-weight: 300;
    font-size: 18px;
    color: #555;
}

h1,
h2,
h3,
h4,
h5,
h6 {
	font-family: "Raleway", Arial, "Helvetica Neue", sans-serif;
}

Hi, the release notes should all be in the readme.txt file in the theme. For the latest version (with listings of all prior versions) it is on github.

But specifically, here is v1.7 and v1.7.1…

= 1.7.1 =
* Quick fix to suppress an error message about libxml invalid tags when processing the site footer. This would only display when WordPress was in debug mode (like on a test site), but it was annoying anyway. If anyone cares, the “error” is really a warning that PHP’s libxml doesn’t yet understand HTML5 tags. It still processes them just fine, though.

= 1.7 =
* Increased the font size for the extra large icon (“icon-xlg”) to 72px (was 50px). Reduced padding to 5px for that as well as the large icon (“icon-lg”).
* Added support for the new <title> tag introduced in WordPress v4.1. It enhances consistency across all WordPress themes for plugins that modify the output of the page title.
* Added two new utility functions to look for files first in the child theme directory before looking in the parent. This allows you to copy down more files into your child directory to edit them.
* Removed bottom margin on alignment CSS tags (alignleft, alighright, aligncenter). This provides more flexibility as margins (or padding) can be added with other CSS tags.
* Finally completely squashed that pesky bug where a bogus page subtitle was sometimes displaying on blog pages.
* Rewrote the Footer widget area logic to more reliably handle from 1 to 4 widgets. Specifically, 4 widgets now collapses to 2 rows of 2 widgets on tablets without causing any display issues.
* Fixed an issue where the Jetpack Carousel plugin, when activated, was getting messed up by the Bootstrap “thumbnail” CSS class. You are now free to use that plugin without issues!
* Fixed the ` tag so that it doesn’t cause extra line-breaks. You can now use “code” when you want it to display inline and “pre” when you want it to appear as a block on its own.
* Added text domain to TGM Activation Plugin Recommendations and fixed text domain on the site credits to allow translation
* Fixed a bug where the default sidebar widgets were displaying when a language translation was made on the sidebar name itself. Now the user-added widgets display instead like they should!

Sorry I didn’t get to this sooner. It looks like you are using a different theme now. I’m not sure if you are using an older version of the theme, but on the home page (only the home page), the blue banner saying HOME in your screenshot shouldn’t even display at all.

If you were just testing a page called HOME that wasn’t actually assigned as the official home page (static page) in WordPress, then it would still display like that until you assigned it as the home page.

If you’d like to try my theme(s) again, you can add CSS to reduce the minimum height of that page header (what I call “content header”). This is the CSS line to change or override in a child theme or with a CSS plugin:

header.content-header {
	min-height: 100px;
}

Sorry, I’m not familiar with that plugin. I’m currently implementing a fix to the sidebar when there is a language translation that translates the name of the sidebars themselves, though. So as far as language support for what WordPress provides out of the box, it should be working perfectly soon.

I’m sorry I don’t know enough about that plugin to be able to help.

Awesome, thanks for figuring this out and taking the time to post the solution. This will be very helpful to people that don’t want the header to be cropped.

According to the documentation on add_editor_style, you should be able to override the file editor-style.css in a child theme. That means you should be able to create a blank one or put whatever you’d like in there.