Error for IE8 users after buddypress-fun theme update.

I recently updated my BuddyPress Fun theme and since the update I have been getting reports from users that are using IE8 that they can't get to my website. They get the following error in the address bar: res://ieframe.dll/acr_error.htm#bravegirlsclub.com,http://bravegirlsclub.com/

I saw that there was an update in version 1.4.2 for an IE8 problem, but this seems to be when the problem started for me... wondering if that update might have a bug? Anybody else having this problem?

  • Kimberly
    • Champion of Loops

    Jeff,

    Richie is no longer with us so I will have to forward this to our Lead Theme Developer. She is full on in another WPMUdev project right now and may not be able to get to it immediately. I will notify her ASAP :slight_smile:

    Thanks for being a WPMUdev member!

    Kimberly

  • Jeff
    • Design Lord, Child of Thor

    Thanks Kimberly... I assumed this was the case. I saw another post about one of your theme developers not being with you anymore and figured out it was Richie.

    I appreciate you forwarding it to your lead developer... hopefully it's not a hard fix!

  • Jeff
    • Design Lord, Child of Thor

    So I have been doing a little research on this and found some posts that MAY help... but I wanted to post here and see what you thought/get a little feedback before I performed their suggestions. (Mainly because I'm not 100% sure where to put they snippets of code that they are suggesting to add.)

    The one I'm thinking will work is this:

    Forcefully set the IE compatibility mode to IE7 or IE9 in the header section of your master page For example

    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7">

    (Complete post is found here: http://stackoverflow.com/questions/5004428/ie8-crashes-when-loading-website-res-ieframe-dll-acr-error-htm)

    I'm not sure exactly where this needs to go in the theme files... any help would be appreciated. :slight_smile:

  • Kimberly
    • Champion of Loops

    Jeff,

    The snippet of code, if you want to try it will probably go in your header.php for your theme.

    I did find this referring to jquery updates:
    http://www.wprecipes.com/how-to-use-jquery-1-4-by-default-on-your-wordpress-blog

    seems simple enough, paste the code in your theme function.php but it is an old snippet and don't know if it would call the newest or just the version 1.4 referenced in the post.

    I'm not "hip" to jquery, so let me know how it goes :slight_smile:
    I'd love to know more

    Best,

    Kimberly

  • Jeff
    • Design Lord, Child of Thor

    I also tried this code (found at http://bavotasan.com/2010/force-wordpress-use-latest-version-jquery/ ):

    function current_jquery($version) {
            global $wp_scripts;
            if ( ( version_compare($version, $wp_scripts -> registered[jquery] -> ver) == 1 ) && !is_admin() ) {
                    wp_deregister_script('jquery'); 
    
                    wp_register_script('jquery',
                            'http://ajax.googleapis.com/ajax/libs/jquery/'.$version.'/jquery.min.js',
                            false, $version);
            }
    }
    
    add_action( 'wp_head', current_jquery( '1.7.2' ) ); // change number to latest version

    Still no dice...

  • Jeff
    • Design Lord, Child of Thor

    I think I have pretty well ruled out that it is not a problem with IE8... I've tried just about every recommended solution I could find online and none of them corrected the problem. Here is a list of the things I've tried for the record:
    - use latest version of jQuery
    - force compatibility mode to IE7
    - disable all addons in IE8
    - use no addon version of IE8
    - reinstall IE8
    - theme update

    I also completely changed the theme to another buddypress theme and the problem went away completely. (I changed to Frisco for BuddyPress 1.5.04 by David Carson.) When I changed back to the BuddyPress Fun Child theme, the problem returned. However, I activated the parent BuddyPress Fun theme and the problem went away, so now I at least know that the problem is with the child theme and not the parent theme... now I just need to go compare all the files in our child theme and get rid of everything that I can until the problem goes away... I'll close this topic so none of you have to waste your time on it anymore... :slight_smile:

  • Kimberly
    • Champion of Loops

    Jeff,

    So, have we established that your child theme is the issue?

    If you remove the style.css then it will work?

    Perhaps something in that is causing the conflict...

    How much customization do you have? Can you try to see if you can swap that one with a new one. i.e. take that one out, put on your desktop, remname for the time being, toss in another with a quick test customization, and see if that works?

    Perhaps there is something in your customization that is overriding or conflicting with the updates?

  • Jeff
    • Design Lord, Child of Thor

    Yeah I can absolutely try that Kimberly... should I just make a completely empty style.css file to replace it with, or do you have a sample one that I could enter?

    I don't really have much customization in there... just the ones that Patrick and yourself helped me add in that other feed, but the problem was happening before I added those.

  • Jeff
    • Design Lord, Child of Thor

    Here is what is in my child theme style.css file in case that helps...

    /*
    Theme Name: BuddyPress Fun Child Theme
    Theme URI: https://premium.wpmudev.org/
    Description: A BuddyPress theme full of customizability and options - with a heap of fun thrown in. Compatible with WordPress with or without BuddyPress, WordPress MU with or without BuddyPress and WP/WPMU installation with BuddyPress 1.2+ only.
    Version: 1.3.2
    Author: Richie KS at Dezzain Studio (incsub)
    Author URI: http://dezzain.com
    WDP ID: 92
    Template: bp-fun
    Tags: buddypress, White, Blue, Three Column, Two Column, Right Sidebar, Fixed Width, Custom Colors, Custom Header, Theme Options, Threaded Comments
    
    Copyright 2007-2010 Incsub (http://incsub.com)
    The CSS, XHTML and design is released under GPL:
    http://www.opensource.org/licenses/gpl-license.php
    
    changelog
    v1.3.2
    - fixed function error when buddypress not activated/installed
    
    v1.3.1
    - add redirect options in privacy theme settings
    - refine load_theme_textdomain() function call
    - add multi category selections for featured article and featured slideshow
    - add new custom widgets like flickr, twitter and featured post multi-category widget
    
    v1.3
    - added new WordPress 3.0 custom menu support
    - added featured articles options for articles mode or slideshow mode with attachment or custom field thumbnail options
    - added multi level drop down navigation
    - added compatible with latest WordPress 3.0 and BuddyPress 1.2.5.2
    - replace incudes() with locate_template() for better child theme support
    - fixed language missed localize
    - core templating changes with added lib folder
    - fixed bug trac
    
    v1.2
    - add border line for activity stream
    - update adminbar to new bp 1.2 style
    - fixed adminbar dropdown missing in sub blog
    
    v1.1.9
    - skip version
    
    v1.1.8
    - Updated documentation
    
    v1.1.7
    - fixed recent sitewide blockquote padding issue
    - fixed group item-content css overlay issue
    - replace php theme option stylesheet with style sync theme option for better compatible with various server host
    
    v1.1.6
    - added compatible with BuddyPress 1.2+
    - added compatible with single wordpress install or wpmu install with or without BuddyPress enable.
    - frontpage activity stream support
    - added child theme support
    
    v1.1.5
    - added privacy option and article block on and off
    - added global adminbar option
    - fix components css
    - fixed directory templating
    - img overflow fixed
    - added the ability to let only admin and mod create group
    - added widget to profile page
    - add default style for extra component without breaking the original css.
    
    v1.1.4
    - fix forum directory css
    - fix double facebook fbc_login with bp-fbconnect
    - fix adminbar css across all blogs
    
    v1.1.3
    - facebook core code changed that changed their css fb_login needed to recss
    - remove current-site option in navigation so site link did not link to main blog
    - you can comment out the main-entry.php if you do not want to used the home news feature
    
    v1.1.2
    - added support for facebook Connect plugin
    
    v1.1
    - added compatible with bp 1.1 new theme structure
    
    v1.1.1
    - Updated documentation
    */
    
    /* loading wp parent css */
    @import url(../bp-fun/_inc/css/base.css);
    @import url(../bp-fun/_inc/css/global.css);
    
    /* loading bp parent css */
    @import url(../bp-fun/_inc/css/default.css);
    @import url(../bp-fun/_inc/css/bp-css.css);
    
    /* loading parent theme custom css */
    @import url(../bp-fun/_inc/css/custom.css);
    
    /* loading parent theme adminbar css */
    @import url(../bp-fun/_inc/css/adminbar.css );
    
    #custom #top-header .top-h {
    background:url("http://bravegirlsclub.com/images/blog-header-image11.jpg") repeat scroll 0 0 transparent !important;
    height:195px ;
    }
    
    #top-header .site-title {
    display:none;
    }
  • Jeff
    • Design Lord, Child of Thor

    I deleted all of the changelog and the references to import the parent stylesheets and it looks like it fixed the problem... now just to verify that with our users...

    Thanks for helping me through this... :slight_smile:

  • Jeff
    • Design Lord, Child of Thor

    I had the same problem... I ended up taking everything out of the child theme's style.css file except for the theme info and my customizations...

    I removed the changelog that was in there, as well as the references to the parent themes css files and it solved the problem for me.

    I would create a backup of the file first, but give that a whirl.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.