page boxes on different pages shows empty box

[sublimity 0]

I have used the Page ID to show different page boxes on 2 different pages. Although it does work, the page box that is not suppose to be on a page (using Page ID) shows up empty (no content in it, but the css styles and div tags show up--making a thin line). Here's the code that shows up:

<div class="fboxes fix">
	<div class="fboxdividers fix">
															</div>
	</div>
	<div class="clear"></div>

Here's a 2 screenshots: (iblog css) iblog css (my css) my css I hope that is clear....thanks

[sublimity 0]

I meant to say "feature box" not "page box"

[kastelic 6]

You mean your using CSS to hide the ones you don't want to see? What do you mean by "I used the page ID".

[sublimity 0]

I just meant that the feature box that should not show up on that page is creating those css tags. The content is not showing up (like it should, because that feature box is for another page, but it is still creating those css tags).

[kastelic 6]

And how you are you hiding that feature box, with CSS or through the page Section Control?

[sublimity 0]

I'm doing everything through the Feature Set up (putting the page id on the feature boxes I want per page) -- I haven't done anything with the css (except my own styling. I showed two screen shots--one with my altered css, and the other with the default css)

[kastelic 6]

Have you tried checking "hide features" on the page that you don't want the feature to appear? (Section Control)

[sublimity 0]

I do want the feature box to show on that page, and I thought using the page id in the future set up would just make those features I want show up on certain pages. And it does work, the feature box I have on the home page is not on the services page, but there is a line below the feature box. It's like the content of the home feature box is not on the services page, but the css styling is.

[kastelic 6]

I don't know man, I mean, where do you put in the page id? I would just have 2 different "feature sets" meaning each set of features is assigned to different categories. Then when you make the page, just choose which feature set you want to display. Sorry if im just not understanding you. Maybe the problem is more that its showing two feature areas when it should be showing one. Is it possible that in Template Control, you have the features area dragged into a template and also dragged into an element within that template? Which templates are you using for these pages?

[kastelic 6]

Or I guess more of a realistic example of the second possibility above is that you have the features section dragged into the Site Header and also into a page template? As a last resort, are you able to hide the offending bar with CSS? (display:none)

[kastelic 6]

And as a final final resort, if you can't only target one of the feature divs, you may have to use jQuerys nth selector to only target the second one.

[catrina 103]

Can you provide a link to your site?

[sublimity 0]

It's local on my computer, but I just set up iblog pro on my server, and I get the same thing. link to my server I have two pages that use two different set of feature boxes--the home page and services page. I use the "Page IDs - Comma Separated" to specify the home and services page. I'm getting the impression that I only use the same feature boxes on certain page, and not different feature boxes on different pages?

[catrina 103]

I'm getting the impression that I only use the same feature boxes on certain page, and not different feature boxes on different pages?

Since there is a Display Page IDs setting in the feature boxes settings, I don't see why different feature boxes can't be set up on different pages. It says this about the feature box page IDs: if none are set, it will be shown on all pages with fboxes enabled. It doesn't say anything about not specific feature boxes displaying on specific pages...

[sublimity 0]

Yeah, it does work sort of....both the home and services page have their feature boxes on them, but then it creates that line below each one. And looking and the source code, that line has the same css styles as a feature box, but it is empty. And that is what I want to get rid of.

[catrina 103]

Add this CSS code to your custom code area:

div.fboxes div.fboxdividers {display: none;}

[sublimity 0]

I just did that, and I got a strange result.

[catrina 103]

Ah, it took away the boxes too. Take that code out and replace it with this:

div.fboxdividers {display: none;}

[sublimity 0]

I create a page called "show feature box"-- it has the show feature box checked, but the id of this page has not been added to any of the feature boxes created, but it still shows that line.

[sublimity 0]

looks pretty much the same....

[catrina 103]

I think you're going to have to go into the parent file (template_fboxes.php) and just get rid of it that way. This is what you want to look for and delete:

<div class="fboxdividers fix">
					<?php endif;?>
					<?php $count++;?>
				<?php endif;?>
			<?php endforeach;?>
		</div>

After saving check to see if the line is still there.

[sublimity 0]

Okay, I will do that. Thank you for your help. I just did it, got an error: Parse error: syntax error, unexpected $end in /home/sublimit/public_html/wordpress/wp-content/themes/iblogpro/pro/template_fboxes.php on line 27

[sublimity 0]

I just put it back. I have to attend to some other things. Again, thank you for your help. I'm thinking it's a bug?

[catrina 103]

Okay, open the file again and add the code you just removed back where it was. I think CSS would be the best way, but the problem is, it's also taking away the entire fbox area...

[sublimity 0]

I agree....changing the css will affect the whole thing. I think it it's a bug--as far as I know, I'm following the directions of what is says to create feature boxes and have it go to certain pages. When I added that last page "show feature box" - it has that box checked "Show feature boxes (from feature setup) on this page", and I did not include the ID of that page in the feature box set up--so none of the feature boxes are on that page, just that line.....very strange.