gpaciga
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: 2.0.3 & Blogger importI took a look at your idea, taintme, and yeah, it seems like the atom feed blogger puts out only has 100 posts. You could delete the posts successfully imported, republish, and important again since the atom feed will have the next 100 posts. Marking them as draft, so you don’t loose them from Blogger all together, should have the same effect. You’re still stuck doing comments manually though. Once I get my template the way I want, if this problem isn’t fixed, I’ll do the feedburner RSS import.
Forum: Fixing WordPress
In reply to: 2.0.3 & Blogger importThe details only mention Textpattern and Dotclear, so it doesn’t sound like it….
I tried getting an account on wordpress.com and importing my blogger blog there, but encountered the same error. That makes me think it’s a problem with Blogger, and I’m doomed to copy and paste each entry manually ??
Forum: Fixing WordPress
In reply to: 2.0.3 & Blogger importI noticed when the Blogger page is displayed after spitting out that array, the fields all have a backslash and quotation mark like \”this\” where I wouldn’t expect them (i.e. the blogspot subdomain field). Might this be causing the “malformed” error later on, or is it just an artefact of printing the data? There are some other threads about backslashes creeping in where they shouldn’t in 2.0.3.
Forum: Fixing WordPress
In reply to: 2.0.3 & Blogger importSorry for the double post but I don’t think I can edit my last one… It turns out that once in a while (maybe 1 in 5 tried) the importer gets past the error at blog-publishing, but then after publishing 100% I get the same error as taintme:
malformedYour Blogger blog did not take the new template or did not respond
Forum: Fixing WordPress
In reply to: 2.0.3 & Blogger importI’m having the same error described in the original post. At the blog-publishing stage, the importer prints an array like those already shown and a text version of the Dashboard page which sets the publishing settings. It looks like it was trying to set the blog to publish to Blog*Spot, but hit an error. Any help would be greatly appreciated.