jmjf

Full width is intended to have no sidebars–it’s full width. If you want sidebars, use the default page template. Or you can build a custom template based on page.php. A custom template will allow you to create a custom sidebar or build custom widget areas on the page.

Having thought about this, my vote is for <h3> based on the idea that <h1> is the site title (most important), <h2> is the post/page title (next most important), and everything else on the page should be subordinate to those (<h3> or smaller).

See this pull on github, but note that it seems to be pulling in some other changes (my git-foo is weak, as noted in the pull). You may want to identify the changes described and apply them by hand.

https://github.com/obenland/the-bootstrap/pull/48

I just happened to be crawling through this section of the-bootstrap recently for my own purposes, so I have an idea of where to look. Here goes.

The pubdate message is related to the Posted On date in the entry header (which comes from the appropriate partials/content-xxx.php file). The date comes from the_bootstrap_posted_on in template-tags.php, and it is using pubdate. There seems to be mixed advice about this. On the one hand, W3C says they’re dropping it. No, we aren’t. Yes. No! Maybe! And other sites have a mix of recommendations to use it or not. It appears to be related to RSS feed publication. I’m not sure if this should be kept or dropped without some further research.

The complaints about rel=”category tag” are related to the category links at the bottom of the post. As best I can tell, the-bootstrap gets this by calling WordPress’s get_the_category_list function. Sure enough, the code in WP is injecting this. This seems to be a known issue in WP (though one they’ve apparently chosen not to fix). There’s a simple way to remove it here. https://www.whitneykrape.com/2011/07/quick-fix-for-relcategory-tag-in-wordpress/

The legend tag is around the Leave A Reply heading on the comment form. According to W3C, it should only be used as the first child of a fieldset, hence the validator’s complaint. The tag is coming from the_bootstrap_comment_form_defaults in functions.php, specifically the title_reply and title_reply_to values. I’m thinking it should be removed given W3C’s guidance. I’ll try to put up a pull on github tomorrow.

Finally, the border warning is related to the Share/Save image in your footer, which seems to be coming from your Add To Any plugin, based on the class applied and the fact that it’s pulling from addtoany.com. It’s applying a border attribute to the img, which apparently obsolete.

Hope that helps.

I have several plugins that use shortcodes (WooCommerce, a FAQ plugin, etc.). They work fine for me. (Except WooCommerce requires a lot of work to fit into a Twitter Bootstrap style, but I think that will be true of any full-featured eCommerce plugin.)

To be sure, I installed Easy Digital Downloads from https://www.ads-software.com/extend/plugins/easy-digital-downloads/ (since you mentioned that plugin specifically).

Then I created a page and put the [downloads] shortcode on it. Viewed the page and it said, “No Downloads found.” That made sense. I hadn’t added any. So I added a download. Refreshed the page. It showed my download. I put some text in front of and after the shortcode. Refreshed the page. Everything still worked.

Based on that test, I’m going to suggest that something besides the-bootstrap is causing your shortcodes to fail. Perhaps one of your other plugins or some theme customization you did.

Your statements about update cycles are incorrect. Plugins and themes (should) update when they need to fix a bug or provide new features, not with every minor release of WP. Based on information in the plugin library and the plugin stylesheets linked in your page source, several of your plugins did NOT update with the 3.5.1 release (Jan 24, 2013), several didn’t update for 3.5 either (Dec 11, 2012). For comparison, the-bootstrap was last updated on Dec 22, 2012, according to the theme library.

To properly diagnose your problem, start by turning off all your plugins but one that is uses shortcodes and is failing. Test that plugin alone. If it doesn’t work, you may have something wrong in your custom page templates and other theme customizations. In that case, switch from your child theme to the main the-bootstrap theme and test the plugin. If that doesn’t work, your base the-bootstrap has probably been modified, in which case you should test with the clean parent theme. Once you have the first plugin working with a shortcode, start activating plugins one at a time to see which one breaks the shortcodes. If you don’t have a test site, but you may want to set up a copy of your site using something like XAMPP so you aren’t testing in production.

Hope that helps.

Well, I see what you say happening when I turn off my custom nav menu in the customizer.

There are some problems with enabling what you say you want. WordPress’s default menus rely on the page hierarchy and (critical point) include links to parent pages on the menu items for those pages. That means when you touch/click on a menu item with children, you’ll go to the page instead of expanding the submenu of children. In a non-touch environment, you can use hover to drop menus, but there is no hover in a touch environment. Alternatively, you could write custom code to build the menu, but then you don’t have links to the parents in your page hierarchy.

Note, some WP users have worked around this and enabled hover instead of click, but that breaks their menus on touch devices. But if you’re going to break on touch devices, why bother with a responsive theme? It’s almost impossible to find a non-touch screen <1024px, so if you’re going to break on phones and tablets anyway, use a fixed 940px or 960px layout.

You’re posting multiple threads about the same basic problem, which is how drop down navigation menus work on touch devices. Think about it. Touch devices don’t have a hover option, only click. So when you touch the top level nav item you can either drop the menu under it or go to the page the item references, not both. This is the nature of touch interfaces.

I don’t have an iPhone, but I have noticed that menus with more than one level below the main nav don’t work well on touch devices in general. I think this is, in part, due to the nature of touch devices. My approach has been to have one level of menus below the nav. Ultimately makes it easier for the user too.

Do you have a link to the site? Because I don’t see an “in” in the nav menu classes.

Also, you should work in a child theme, not directly on the base theme. Otherwise, if you update the-bootstrap, you lose all your changes.

content-page.php will be called for every page, so if you want to remove the title for every page, you can make a copy of partials/content-page.php into a partials directory in your child theme and remove the line.

If you just want to remove the title for the home page, you can write a custom page template for your home page. I did that and didn’t call partials/content-page.php because I’m doing some very different stuff on the page.

Another option might be to set it up in CSS. The <body> tag for the home page includes the class “home” so you might be able to write CSS in styles.css that will affect h1.entry title only when in body.home. Maybe something like body.home > h1.entry-title { make it invisible } — but I haven’t tested that CSS, just am speculating based on some other examples I’ve seen.

I don’t have a clear understanding of exactly what’s going on, but I’ll share what I know.

In the-bootstrap, partials/content.php calls the_excerpt() to get the excerpt for an entry (but only for searches). The codex says the_excerpt will include […] but doesn’t include a read more link.

I wrote a customized partials/content.php that always called the_excerpt(). Everything I tried to remove the link was unsuccessful until I wrote my own excerpt function (see last post in thread linked earlier) and called it instead of the_excerpt(). Other people on that thread were able to get the remove filter calls to work. Your mileage may vary.

While I was experimenting with excerpts, I found that calling the_excerpt() and adding a read more link would result in a double read more link, so it seems something is going in the-bootstrap to add the read more link, but I haven’t been able to track it down. I needed to customize a copy of partials/content.php (with a different name) anyway because that’s the only way I could find to force excerpts in a list on my home page, which I want to keep reasonably short (by default, the-bootstrap only shows excerpts for searches).

Maybe there’s a better way to do it, but that’s what I found that works. Maybe post on that thread and someone there will have more help.

opticom_erik seems to have nailed it. The page source shows 2.0.3 and 2.0.1 versions of the js in judic’s page.

I note you (erik) dropped 2.2.2 in favor of 2.0.3. FWIW, I’m running 2.2.2 in my test site with no menu problems. (Of course, I’m only loading one version of the js.)

Changes that work in my test environment submitted to github.

Note that these changes expect to find the following files in the child theme.
css/bootstrap(.min).css
css/bootstrap-responsive(.min).css
js/bootstrap(.min).js

https://github.com/jmjf/the-bootstrap/commit/3939244b587b32c8d44a06fd1940068e5a805ba3

https://github.com/jmjf/the-bootstrap/commit/5337ad2c6168337515c8536b9159965e968d1842

Note comment on the last commit which explains what actually changed since github seems to have gotten lost in the diff.

Or, add a new theme option for “child theme css” like the bootswatch options. That’s really what’s going on here.

(I guess I’m making notes to myself here in case I do this.)

Bootstrap (the framework, not just the-bootstrap theme) doesn’t do menus like most WordPress themes do menus. It gets into the whole touch-centric devices realm where there is no hover, only click. The practical result is, you can’t have a link on the top-level of a drop-down or Bootstrap (and therefore the-bootstrap) will assume you want to go to that link when you hit the top-level.

You have several options within a Bootstrap-based theme that doesn’t rewrite Bootstrap’s menu behavior.
1) You can have a top-level link that goes to the blog page, but with no drop-downs because Bootstrap is touch-friendly and will never show them.
2) You can build a custom menu in the Dashboard (make the top-level blog item a custom link to #) and add each post you want under the blog menu item there. This seems like a lot of maintenance.
3) You can use a custom home page with a section listing blog posts or a carousel to make the latest blog posts visible on the home page.
4) You can try to work around Bootstrap by enabling hover on the menus, but then touch device users won’t be able to use your site properly. I saw a recent study from a major research firm that said over 50% of internet users use a touch device (tablet or smartphone) for at least some of their internet access. Do you really want to alienate all those people?

There may be a few other options like a featured posts widget or something else to draw attention to key posts.

On the one hand, the menu thing is my main Bootstrap peeve. On the other, when I test menus on a WordPress site from my phone, doing it the old WordPress way doesn’t work, the Bootstrap way does work. Given the way tablets and smartphones are overtaking PCs as internet access devices, I’m designing my site and menus to work well for both touch and mouse users within the boundaries of the Bootstrap way.