WordPress.org

Support

Support » How-To and Troubleshooting » [Resolved] Unable to import blogger

[Resolved] Unable to import blogger

  • For the past two day I have been unable to import my blogger account into wordpress, I get the following error message:

    Something went wrong. If the problem persists, send this info to support:

    HTTP/1.0 403 Invalid AuthSub token.
    Content-Type: text/html; charset=UTF-8
    Content-Length: 167
    Date: Fri, 06 Aug 2010 20:16:35 GMT
    Expires: Fri, 06 Aug 2010 20:16:35 GMT
    Cache-Control: private, max-age=0
    X-Content-Type-Options: nosniff
    X-XSS-Protection: 1; mode=block
    Server: GSE

    <HTML>
    <HEAD>
    <TITLE>Invalid AuthSub token.</TITLE>
    </HEAD>
    <BODY BGCOLOR=”#FFFFFF” TEXT=”#000000″>
    <H1>Invalid AuthSub token.</H1>
    <H2>Error 403</H2>
    </BODY>
    </HTML>

    Can anyone help me out to solve this problem?

Viewing 15 replies - 1 through 15 (of 26 total)
  • getting this as well. Looks like there was a similar issue on wordpress.com and they’ve gotten it fixed….
    http://en.forums.wordpress.com/topic/import-error-importing-from-blogger-to-wordpresscom

    This is also posted in the blogger importer plugin section:
    http://wordpress.org/support/topic/plugin-blogger-importer-its-broken-google-accounts-dont-authorise

    Thanks,

    I hope that they can fix this soon, if they could fix this problem over at wordpress.com i don’t see why they can’t fix it here as well.

    Moderator James Huff

    @macmanx

    James, thanks for the link – I had found that before but some of the conversion tools insert additional information and the importer worked FABULOUSLY less than a month ago for me; the workaround is fine for getting the job done but it doesn’t fix the fact that the importer is broken somehow. Something has obviously changed, probably on Google/Blogger’s end, and there has been a fix on WordPress.com, so it seems like it’s probably something relatively straightforward given how quickly they were able to get it fixed.

    James,

    I agree with Katybeth, get the problem fixed instead of trying to figure out a “work around”.

    WordPress.com had the same problem, call over there and see how they fixed it!

    Moderator James Huff

    @macmanx

    Excuse me, MiddletownMike, as a support forum volunteer who gives up his own free time (just like everyone else here) to attempt to help hundreds of users each day, I don’t appreciate your attitude. In fact, I find your response offensive and immature.

    wordpress.com is an entirely separate entity from WordPress(.org). What goes on over there has absolutely nothing to do with what goes on over here. If they make an improvement to the WordPress core over there, and they feel generous, they might roll it into the core over here to be part of a future WordPress upgrade.

    Everyone who works on the WordPress(.org) blogging platform is a volunteer, and the blogging platform itself is offered for free. Perhaps you should check your attitude at the door and find out what you can do to help resolve the problem instead of making demands.

    Since this particular problem has occurred suddenly for most users, I’m inclined to believe that something changed at Google’s end. So, you can either use the work-around, wait for a fix to be rolled into the WordPress core by the volunteers who develop this free blogging platform, or start pointing your fingers at Google.

    James, I completely understand that you are all volunteers and I’m not demanding a fix, just trying to point out that there’s an ongoing issue. Sorry if it came across as anything other than that; that said, is the importer actually part of core? I originally thought so and then realized that it’s actually a separate plugin, albeit one put out by “wordpressdotorg,” but nonetheless requires downloading/installing a plugin: http://wordpress.org/extend/plugins/blogger-importer/

    I was more hoping that by drawing some attention to this, and the fact that it’s been fixed on wordpress.com, that we might catch the eye of someone who is more fluent in this sort of issue to help get it fixed for the .org users.

    Moderator James Huff

    @macmanx

    Sorry, my response was really directed at MiddletownMike’s “get the problem fixed instead of trying to figure out a ‘work around'” and “call over there and see how they fixed it!”

    It wasn’t directed at you in the slightest, and I honestly forgot about your previous response while writing it. I’ve editing the beginning of my response to clarify that.

    Something has obviously changed, probably on Google/Blogger’s end, and there has been a fix on WordPress.com, so it seems like it’s probably something relatively straightforward given how quickly they were able to get it fixed.

    It’s not as easy as you might think. wordpress.com is actually a heavily customized multisite WordPress system. What they do over there to resolve the issue may not work with WordPress itself. It’s also entirely possible that the problem could be related to how your server configuration handles Google’s new changes. This could certainly be a relatively easy fix for wordpress.com (as they control their own servers), but would require a change to be made by your hosting provider, not WordPress.

    is the importer actually part of core? I originally thought so and then realized that it’s actually a separate plugin, albeit one put out by “wordpressdotorg,” but nonetheless requires downloading/installing a plugin

    The importers were removed from the core and turned into plugins to reduce bulk. In future releases, they’ll be identified as “core plugins” (plugins developed and supported by the WordPress team) along with a few others.

    I was more hoping that by drawing some attention to this, and the fact that it’s been fixed on wordpress.com, that we might catch the eye of someone who is more fluent in this sort of issue to help get it fixed for the .org users.

    It looks like the bug hasn’t been officially reported yet. I strongly suggest that you report it to get the attention of the right people. Follow this guide:

    http://codex.wordpress.org/Reporting_Bugs

    Thank you for your patience, and I apologize for the confusion earlier.

    Hi James ~ you saw me on another thread asking about this issue. I’m encountering it still and tried the workaround you directed me to. It gave me an error msg as well (basically, it didn’t do anything)

    You mentioned workaroundS (multiple) what are the others?

    One person I saw uploaded their blogger blog to wordpress.com and then exported THAT and uploaded it to wordpress.org

    Yeah, it’s a Texas Two Step, but it seemed to work.

    Confirming that I’m experiencing the same bug.

    mrmist

    @mrmist

    Forum Janitor

    I vaguely recall that there is an open bug ticket around the blogger importer, but can’t find it just now. It’s probably the same issue, in which case there’d be a fix soon.

    I did enter a ticket/report a bug on this in the Trac, so hopefully we’ll see something soon!

    Moderator James Huff

    @macmanx

    For reference, here’s the ticket: http://core.trac.wordpress.org/ticket/14566

    The authorization and session tokens start with 1%2F and the percent sign gets stripped by the regex patterns.

    Update the regex patterns in the auth() function of the blogger-importer.php plugin:
    Line 99: Added percent sign in regex pattern for authorization token
    $token = preg_replace( '/[^%-_0-9a-zA-Z]/', '', $_GET['token'] );
    Line 108: Added percent sign in regex pattern for session token
    preg_match( '/token=([%-_0-9a-z]+)/i', $response, $matches );

    That worked for me.

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘[Resolved] Unable to import blogger’ is closed to new replies.
Skip to toolbar