cconoly

Where is the “static mainpage” tab?

Thanks, I’m glad you got it working. I am marking this post resolved. Please let me know if you have any other problems in a new post.

Or if you want to just move it over and not effect the width you can edit line 168 of wp-content/plugins/wp-flybox/includes/css.php and add 2 to the position.

echo 'div.wpfb-facebook {width:'.($wpflybox_widths[1]+68).'px;top:'.$wpflybox_pos[$key].';'.$wpflybox_side.':-'.($wpflybox_widths[1]+36).'px;position:'.$wpflybox_position.';z-index:999999;text-align:right;direction:ltr;}';
would change to:
echo 'div.wpfb-facebook {width:'.($wpflybox_widths[1]+68).'px;top:'.$wpflybox_pos[$key].';'.$wpflybox_side.':-'.($wpflybox_widths[1]+38).'px;position:'.$wpflybox_position.';z-index:999999;text-align:right;direction:ltr;}';

I changed the +36 to +38.

This would just move the box and not effect the width of the iframe and box.

I found the problem. Either you edited an id in your themes default.css or the theme edited it. The edited style is:

div.wpfb-facebook {
    margin-top: 100px;
    right: -330px !important;
}

Since it has !important, when you hover, the style cannot change to right:0px; because the important is keeping it set at 330px. So you would need to delete this in your theme’s default.css

If you want the style to be 330px instead of 328px by default then you would need to edit wp-content/plugins/wp-flybox/includes/css.php and change line 140 which has the array that contains the default widths.

$wpflybox_widths=array(
      1 => '292', //facebook
      ...

would need to change to

$wpflybox_widths=array(
      1 => '294', //facebook
      ...

Increasing the default width by 2px is basically doing the same thing you or your theme is doing without having it stuck with !important.

Please try this and let me know whether or not it worked for you.
Thanks!

I found the same problem in the file custom_landing.js, located at:
/wp-content/themes/thematic/library/scripts/custom_landing.js?ver=3.5

This could also be causing the problem. Try commenting out your console commands in all your custom javascript files.

ofsajd, did you create that script or get it from somewhere else. And I agree it should not be in the thematic directory structure.

I got it, thanks.

There is a fatal error in your theme js. It is in file custom_menu.js, located at:
/wp-content/themes/thematic/library/scripts/custom_menu.js?ver=3.5

The javascript logs the position of the facebook tab to the browser’s console. Since IE does not have a console, the browser returns an error and does not execute the command after that which is to show the tab.

To Fix it, edit the file and comment out (with the //) lines 150, 154, 161, 164 where it says:
console.log(jq('.wpfb-facebook-transition').css('margin-left'));

I can see the author of the theme or that script commented out all the other console commands but probably forgot about this one.

This should fix the problem, but if it does not let me know of course!

ojsajd ok if you cant find my email you can send it via https://njarb.com/contact-us/

I installed thematic on a couple of my sites and a fresh install of wp flybox and had no problems in IE 8 or 9. It may be one of your plugins causing a problem. If you have wp-flybox showing on your site now, then you can send me your site address and I can look at it specifically.

It is probably something to do with your theme. What theme are you using?

If you are seeing a blank white when you open the tab it is probably because you have an IE addon installed or set your cookies to strict or some other addon or setting that disables facebook from being able to use cookies or tack you. I had the same problem with a Firefox plugin called Facebook Disconnect. Once I disabled it and cleared my cookies and cache everything worked fine. Can you try viewing it from another computer with IE 8-10 or send me the link to your website so I can try it in a fresh version of IE 8-10? Thanks

Marked resolved.

Please update to version 3.4.
This version includes options to show the plugin on certain pages. Please let me know if you have any problems.

Sounds like a great idea! Look for an update later this week that allows you to control which pages it is displayed on.

I have just released version 3.0 which is much faster. With the 8 slowest tabs on, the highest time I got was 0.7 seconds, and that was at first load. After the first load and when the tabs are cached the highest I got was 0.017 seconds. The caching should help speed it up. Caches last between 4 and 12 hours. I also separated each tab into a separate file so all the functions for all the tabs were not being loaded every time. Let me know if you have different results.