oshawapilot

I’m happy to provide a copy of the .sql dump to one of the mods/admin here who may have some diagnostic ideas..

Email: me at oshawapilot dot ca

Hi Podz;

It errored out at various spots in the import process.

The errors varied, but seemed to mostly relate to sections of the .sql file where comments or such had been inserted by the old version of phpMyAdmin. The new version was not interpreting these commented portions of the file as valid, and would throw an error and stop processing the import.

I tried editing the file on various occasions to the best of my ability to remove as much of the commenting and such as I could, but I either ended up breaking the file and it would simply throw another error at a different spot. Again, I think alot of this comes down the fact that I’m not very fluent with the syntax, and therefore, manually editing the dump files isn’t my forte’.

Hi Moshu;

Sorry, didn’t realize that was verboten around here – my post had slipped completely out of sight and mind.

The original database that I moved (from Phpbb) had to be entirely reworked to reformat it. Untill that point, every SQL import option I tried (bigdump, phpMyAdmin, etc) would choke on the file.

I had a knowledgeable phpbb tech from the phpBB support forums do the rewrite for me, as I’m simply not fluent enough with the syntax, nor was I even completely sure what part of the import it was choking on.

I was very greatfull for his help, and the dump file imported perfectly at my new host after the fact.

Unfortunately I’m not really sure that he would be willing to do the same for my blog (different database formatting I’m sure, which I have my doubts that he’s familliar with), and don’t really feel right asking since he already helped me out once and don’t want to nag.

This is all a result of horribly outdated version of phpMyAdmin which is producing these munged export files. Unfortunately I’m in no situation at this point to request the host update their system, which I doubt they would do anyways.

All of their “preinstalled” software, including their default install of WP, is outdated. The version of phpBB they are installing is 17 versions out of date and full of security holes. They don’t seem to care.

Anyhow, off topic – thanks for the assistance.

Bump.

Ideas anyone?

Ahha! Missed the profile option – that fixed it! Thanks!

Now, I wonder when the rich editor will be remedied?

If I could get the plain (non-rich) editor to work I would definately use it for the time being.

However, even though I’ve deselected the rich editor option, whenever I go to add/edit a post, it still shows up as the default.

(sigh)

Like Poco, I was also able to successfully run the import direct from the WordPress page when I ran wordpress on my local server. Funny he should post that result, as I ended up doing exactly the same thing as he did the evening after I posted my last response, and success.

However, from my “real” wordpress installation (Running the exact same version of WP), the import procedure would fail every time.

On my local installation, it worked perfectly.

So, I took the successfully imported entries from my local installation, and applied them to my “real” live installation..and problem solved.

There is definately something strange going on with the importer though..I’m not sure if it was intollerance on behalf of my web host as to the time it was taking the blogspot.com site to respond, or what the overall issue was, but over several days of trying fruitlessly, it just wouldn’t go.

Sorry to dredge this up again, but is NOBODY else still having this issue? I’ve been trying rather fruitlessly for 2 days now to import my blogger.com account.

I even resorted to a completely fresh WP install tonight, with a new SQL Database, and it still wont import beyind my first 20 or 30 posts…and even those took about 15 attempts to import that far.

It seems, based on my observations, to simply be a “timeout” issue in the import script – I think that the script isn’t getting information quickly enough from either blogspot, or perhaps my own domain, and is simply timing out.

Is there something in the import script that I can change to increase the length of time before the script times out? I strongly suspect that with a little tweak in this regards, the import would go flawlessly…?

Help!

Exact same issues here – I can NOT get more then two or three posts at a time to import from my Blogger account.

I’ve tried Firefox (my usual browser) and even (gack) tried IE to see if it was a compatibility issue.

Same result with both – 2 or three posts import, and then it just seems to either error out, or simply stop. If I reset, it takes me back to the start…and manages to import another 2-3 posts…and freezes again.

Is there ANY other way to accomplish this task? This will take me days at this rate!