Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 1 through 25 (of 46 total)
  • Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    All the latest of everything, but this has been an issue for 4 months.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    OK…just wanted to post the fix for this. I’ll let the JetPack folks know, too.

    To fix this, locate the class-IXR.php file in the \wp-includes directory. Then, locate the following line, comment it out (//) and save it:

    header(‘Content-Length: ‘.$length);

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Speaking of which…anyone have a better Group plugin than BP Gallery that they are using with success?

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    FYI: This is now fixed. It was the BP Gallery plugin with the latest version of WordPress (3.4.2) and Buddypress (1.6.1). But, instead of just disabling the plugin, it had to actually be *moved* from the plugins directory structure.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    @djpaul – Unfortunately, that’s the only way it works. It doesn’t work in bp-custom at all.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Try adding the following to the bottom of your buddypress/bp-loader.php file:

    remove_action( ‘bp_template_redirect’, ‘bp_redirect_canonical’, 2 );

    This will remove the canonical redirect hook that might be causing you some issues.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    I’m still working to get the Group pages to work, but the following allowed me to get the Member pages to work:

    Add this to the bottom of the buddypress/bp-loader.php file:

    remove_action( ‘bp_template_redirect’, ‘bp_redirect_canonical’, 2 );

    This will remove the canonical redirect hook that might be causing you some issues.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Interesting that it wouldn’t work in bp-custom, but had to be placed in bp-loader.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Thanks! Worked like a charm.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    You would *think* BP doesn’t touch XMLRPC at all, but here’s the scenario…

    Pre BP 1.6x – works fine. Windows Live Writer connects and works. JetPack can connect.

    Post BP 1.6x – With BP activated, Windows Live Writer cannot post to WordPress. You have to disable BP before JetPack will connect correctly – gives error about XMLRPC. So, something that BP is doing when enabled, locks XMLRPC.

    I’ve reported this to the JetPack folks and they are checking into it.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Gave it a shot, but had no affect. Same issue. If I could get the profiles issue resolved (too many redirects), I can circle back to the others. It’s just strange that Buddypress “locks” the XMLRPC file.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Any takers?

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    @swaggstar Where in BP-Loader.php did you place the file? I’m having the same issue and have been since 1.6.x released.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Anyone attempted a stab at fixing this specific issue?

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    @marc-birkett So…what exactly did you add to your web.config? Your link talks about the htaccess file which isn’t available for IIS.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Yeah…it seems that’s a common suggestion — permalinks, page recreations, etc., etc. I’m seeing more and more folks with this same issue and it’s really not grabbing the proper attention. I have the exact same issue and have been digging through code for two weeks to try and locate exactly what 1.6.1 did.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Same issue here and reported by others. Would be nice to see someone take a stab at figuring this out.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    OK…cool. Looking forward to the 1.6.1 update!

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Bump

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Yep…definitely issues. I’m wanting to downgrade, but don’t see any downgrade instructions posted anywhere. I’ll just have to wait until there’s a more significant reason to upgrade instead of just having the latest and greatest.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Same here. Still waiting to figure out if someone will produce a fix for this version.

    Avatar of rodtrent
    rodtrent
    Participant

    @rodtrent

    Same here. Still waiting to figure out if someone will produce a fix for this version.

Viewing 25 replies - 1 through 25 (of 46 total)