Kubrick – including sidebar in pages

meagan
(@meagan)

19 years, 2 months ago

I’m using a slightly modified Kubrick template and I’ve noticed that when I click on a page link, the page comes up, but my sidebar disappears. I’d like for the sidebar to be visible on pages just like they are on posts.

How can I manage this?

Viewing 12 replies - 1 through 12 (of 12 total)

NuclearMoose
(@nuclearmoose)

19 years, 2 months ago

Meagan,

Are you using the Kubrick template with V1.2.2 or with V1.5 because there is a difference between the two.

I’m going to assume that you are using WP V1.5 — you have to ensure that the function call to include sidebar.php is included on any pages where this content is desired.

Thread Starter meagan
(@meagan)

19 years, 2 months ago

It is V1.5.

I put the sidebar.php include right above the one for footer.php in page.php. The sidebar is there, but it appears at the bottom right, under all my content.

Can you suggest how I can arrange the include in page.php so the sidebar is a sidebar and not just at the bottom of the page? I fooled around with some of the div tags, but that only moved the sidebar farther to the right and changed the font.

Thread Starter meagan
(@meagan)

19 years, 2 months ago

Well, if anyone else was having the same problem I was, I found the problem.

<div id=”content” class=”narrowcolumn”>

in page.php was “widecolumn” and apparently that was restricting the room for my sidebar.

dawg
(@dawg)

19 years, 2 months ago

could you explain the method for 1.2.2 as i have read thru these posts on side bar s but this error is what i get Thanks in advance

my error
http://cafe789.com/kyles_eyes/index.php?p=31#comments

ecuneo
(@ecuneo)

19 years, 1 month ago

I am currently having the identical problem which seems to have appeared out of nowhere. The side bar will not appear alongside of the main content, but instead shows up at the bottom right after all the postings. The solution of “content class=”narrow column” was not relevent for me as the original coding in page.php was correct. I have recopied all the theme modules up to the site with the hopes that I would overlay any problems I may have created while experimenting with CSS. …didn’t work. The theme modules are now pristine except for header.php which calls for my header.

http://www.magiccityjazz.com/EdsBlog/

dirty8
(@dirty8)

19 years, 1 month ago

Edsblog person –
When I click your link I get a blank page, but I had the same problem and it was because I’d moved a </div> in one of the php files. I can’t remember which one now.

ecuneo
(@ecuneo)

19 years, 1 month ago

I don’t have a clue about this. I am getting ready to abandon this package. I don’t need this crap. I just can’t get it to work in the default mode. “classic “works fine. And many of the newer themes are showing up buggy on my ‘puter. “Gila” will not run at all past the header. My server is running PHP 4.3.10 and SQL 4.0.22 standard. I will add that this forum is not proving helpful in any way. Why all the accolades?

Moderator James Huff
(@macmanx)

Volunteer Moderator

19 years, 1 month ago

Try the Kubrick AllSidebar edition: http://wordpress.org/support/topic.php?id=25616

jhesch
(@jhesch)

19 years, 1 month ago

ecuneo, you have an extra </div> in your code. I was going to tell you where it is but it looks like you switched back to the classic theme so I can’t take a look. Download a new install of WordPress and pull out the default theme folder and upload it to your server replacing what you currently have.

ecuneo
(@ecuneo)

19 years, 1 month ago

Thanks people. I’ll work on it. I’m switching back to default so anyone who wishes to, can take a look. I have rebuilt the ‘default’ theme folder several times.

To: jhesch.
I’ll download a new one as you suggest and then rebuild the folder.

To: macmanx
I have downloaded the allsidebar version but have not installed it as yet. I’ll get to it tonight.

davereed
(@davereed)

19 years, 1 month ago

It seems pretty easy to me. Maybe I’m doing it wrong, but it seems to be working.

In the V1.5 template you just need to insert

<?php get_sidebar(); ?>

toward the bottom above

<?php get_footer();?>

in the single.php file.

swanderson
(@swanderson)

19 years, 1 month ago

I am working with a new install (except for the database) of WP 1.5. All 1.2 files were deleted off the server; the install was done with Fantastico. It went well.

I am using the theme Sharepoint Like from Alex King’s contest page as my main theme. I have done some customizing, but only on the index and style files in the Sharepoint theme. I have added the Searchform in the sidebar. I have also installed the Breadcrumbs plugin and the Nicer Archives add-in.

If I switch themes, the sidebar is messed up in the main blog page view in every theme but Sharepoint. In Default theme, it’s pushed down below the end of the bottom-of-post, “prev pages” item. In Classic view, the sidebar starts at the top but is incomplete and the items are out of order. In Journalized Sand, a 3-col theme, the sidebars drift toward the middle of the last post, overlapping it.

In Journalized Sand, the comments page left sidebar positions properly, the right one is out of position. (A couple of days ago, the comments page view of Journalized Sand displayed properly, although the main blog page was messed up as described above. ) The other theme comments pages, except Sharepoint, display wrong.

Also, in the Default theme, I checked for the widecolumn entry, as one poster mentioned above, and tried inserting <?php get_sidebar(); ?> as Dave Reed suggested above. This made no difference in the way it displayed.

Here’s what I don’t understand. If WordPress is reading the index and style files <i>from the active theme only</i>; and if I’ve only modified the index and style files in <i>one theme,</i> Sharepoint Like â€�? how can the Default, Classic and Journalized Sand themes’ page views be messed up in their displays?

Note that I had developed the same dropped-down right sidebar problem in my previous 1.2.2 installation. I was able to fix it in <i>either</i> the main blog page <i>or</i> the comments page view, <i>but not both</i>, by working with div tags. That’s a big reason why I finally threw in the towel and decided to go with a fresh install of 1.5 and adopt a new theme.