Feature slider navigation buttons

[pmac 0]

Using Whitehouse Pro. Looks like the play / pause and navigation buttons for the feature slider have vanished. Anyone have any ideas as to why this might be?

[cmunns 16]

Did you accidentally disable the option? If not do you have a link to the site?

[pmac 0]

Did you accidentally disable the option?

It is actually exhibiting bizarre behavior. 1) The navigation controls and buttons are not present with FF IE or Chrome, but they are present with Safari on my ipad. 2) I have the feature navigation mode set to "use feature names" however when viewing with my ipad, it is is using numbers instead.

do you have a link to the site?

Thanks, I appreciate that but I would rather not. The content on the site is somewhat controversial and I don't want create a stir.

[cmunns 16]

You need to check for js errors caused by plugin conflicts. That is likely the cause of the feature nav not showing all together in those certain browsers.

[pmac 0]

I disabled all of the plugins including Askimet and it is still exhibiting this behavior.

[catrina 103]

Have you tried checking for js errors in Firefox by going to Tools > Error Console?

[pmac 0]

Have you tried checking for js errors in Firefox by going to Tools > Error Console?

Thanks for the suggestion. Yes I just tried it and it shows no errors on the page.I am totally stumped here.

[catrina 103]

Were the buttons working when you started using the theme?

[pmac 0]

Yes they were. I am not sure when they stopped working but I am assuming it was when I updated WP. Not 100% sure though.

[catrina 103]

Yes, it could be because of the WP update if that's the only change you made.

[pmac 0]

But in that case you would think we would have a ton of people complaining that the theme is busted in 3.1 but as far as I can tell, that's not the case. I see the code... it just won't render

<script type="text/javascript"> /* <![CDATA[ */ var $j = jQuery.noConflict(); $j(document).ready(function () { //Feature Cycle Setup $j('#cycle').cycle({ fx: 'fade', sync: 1, timeout: 10000, speed: 1500, pager: '#featurenav', cleartype: true, cleartypeNoBg: true }); //Overide page numbers on cycle feature with custom text $j("div#featurenav").children("a").each(function() { if($j(this).html() == "1") { $j(this).html("Feature 1");} if($j(this).html() == "2") { $j(this).html("Feature 2");} if($j(this).html() == "3") { $j(this).html("Feature 3");} if($j(this).html() == "4") { $j(this).html("Feature 4");} if($j(this).html() == "5") { $j(this).html("Feature 5");} if($j(this).html() == "6") { $j(this).html("Feature 6");} }); // Play Pause $j('.playpause').click(function() { if ($j(this).hasClass('pause')) { $j('#cycle').cycle('pause'); $j(this).removeClass('pause').addClass('resume'); } else { $j(this).removeClass('resume').addClass('pause'); $j('#cycle').cycle('resume'); } }); }); /* ]]> */ </script>

[kastelic 6]

It would be hard for me to find the problem without seeing the site. If you want to send the url to the contact form on my website (look me up in the pros page) I can check it out for you, and also post it to the developers basecamp area so only devs can see it, if you don't mind.

[pmac 0]

Thanks Jimmy, I sent you the info.

[kastelic 6]

I think whats happening is that there is just too much text in the features text area, and its pushing the controls out of the box. If you can, try reducing the amount of text (it will adopt the height of the longest one). If you want to free up more room, paste this in your Custom Code -> Custom CSS area:

.fcontent .fheading {margin: 0;}

[pmac 0]

Thanks Jimmy, I wish that was the case. I reduced the text in the features to one sentence and the navigation controls still won't show up in FF, Chrome or FF. They do show up however when I view the site on a mobile device such as iphone or ipad.

[pmac 0]

I just tried it using on an online browser emulator and it works in Safari (kind of) I have the feature navigation mode set to "use feature names" however when viewing with Safari,it is is using feature numbers instead. Bizarre.

[kastelic 6]

Hmm, are there any plugins activated that could be conflicting? If not here's a bandaid fix that you can paste into Custom Code -> Custom CSS

#featurearea {margin-bottom:30px;}
	#feature-footer {
	position:absolute;
	width:942px;
	}

[pmac 0]

Thanks for the band-aid fix Jimmy, I appreciate it. Works a charm. I deactivated all of the plugins and I had the same behavior.