All that is required in the header.php file is to use conditional code saying if front page, wrap site title in h1 tags else h4 and then set the post/page titles by default to h1, which is what they should be IMO.
It appears that this might have something to do with that private/public options of blocking search engines. I signed up with a dummy account and upon registrtation selected to block, and it didn’t show on my user page. I went in and changed the option to not block search engines and then it showed. I tried that on the blog in question, but no luck.
John, I tried your technique, but when not logged in, it leaves that space that would normally be occupied by the admin bar just blank space. I wish there was a way to call the admin bar like a navbar, put it in it’s own <div> and then not have the admin bar overlay everything.
Ok, so where can I hack the wp_footer – what I was hoping to do was drop a <div class=”clear”></div> after it so that the <body> can start AFTER the menubar. My issue is that with a background image that sits up top, the logo won’t align with it when the admin bar exists. When not logged in and there’s no admin bar, it’s fine. But the admin bar showing will push down my logo and therefor not align with my background image.
Can you tell me which file specifically calls the admin bar? I see the bb-core-admin.php file in the directory, but can’t find the file that actually calls it.
Forgive my ignorance, would this go in the home theme’s base.css or the admin bar’s css? I put it in the base.css, but it didn’t really work, What I’d like to do is have the admin bar just be at the top, and then just have everything start below it. Another question, is what file is the admin bar actually called?
I would say so, as most people who use WP and WPMU that use permalinks a certain way would like to continue to. Also consider the fact that people using MU with the permalinks as I had mentioned are using them successfully, which means if they install BP onto their MU version, it will create an issue with all of the posts they have.
Thanks, the weird thing is that the month and name permalink structure of /%year%/%monthnum%/%postname%/ will show the comments, but when you strip that down to /%postname%/ it won’t show them.
It’s definitely a permalink issue, as when I set it to %postname%.htm like I normally do on my standard WP installs, the comments don’t show – but when I set it to the default permalinks, the comments show.
Thanks for the help, I’ll figure out a way to get pretty permalinks to work and still show comments… it looks like any custom permalinks have issues showing comments.
Trent & Andy – just emailed you both the domain I’m testing this on. You can click on the comments in the recent comments widget, and you’ll see it takes you to the single page without comments. Just thinking I am missing an enable/disable comments option in the BuddyPress dashboard or something…
Moreover, even on the post page the place to enter a comment isn’t even there (meaning the comment form) I was only able to make the second comment by replying to the default comment within my dashboard. I have checked to ensure that the <?php comments_template(); ?> call is in the single.php file – but not showing on each post.
On the main site, I made a post. I click on that post, and the entire comment block is not showing. Meaning you can’t see the comments that have been made on the post. Even if go to the Blog link in the main navigation, it shows the post with the comments icon and the 2 by it, so the comments exist… but just don’t show on the single page.
