Importing Blogger to Wordpress - memory size error

PHP programming forum. Ask questions or help people concerning PHP code. Don't understand a function? Need help implementing a class? Don't understand a class? Here is where to ask. Remember to do your homework!

Moderator: General Moderators

simonmlewis
DevNet Master
Posts: 4435
Joined: Wed Oct 08, 2008 3:39 pm
Location: United Kingdom
Contact:

Re: Importing Blogger to Wordpress - memory size error

Post by simonmlewis »

I now get this error:

[text]
Warning: Invalid argument supplied for foreach() in C:\xampp\phpMyAdmin\site\wp-content\plugins\blogger-importer\blogger-importer.php on line 227[/text]
Love PHP. Love CSS. Love learning new tricks too.
All the best from the United Kingdom.
simonmlewis
DevNet Master
Posts: 4435
Joined: Wed Oct 08, 2008 3:39 pm
Location: United Kingdom
Contact:

Re: Importing Blogger to Wordpress - memory size error

Post by simonmlewis »

I abandoned it for Blogger Import Extended.
This connects with the Blog itself and imports it all, including images. It works!
Problem though - the images along are over 400MB. When I use Wordpress's Duplicator tool, it fails. It gets to 300mb ish, and says the build was interupted. It only takes about 15 seconds to get to that stage.

Is there a setting in Wordpress that sets the "time" at which it "processes"... ?? Like the PHP Input time ?

There is no guarantee it will install on the hosts server, but that's down to them. I just want to get the Installer file ready.

https://wordpress.org/plugins/duplicator/
Love PHP. Love CSS. Love learning new tricks too.
All the best from the United Kingdom.
User avatar
Celauran
Moderator
Posts: 6427
Joined: Tue Nov 09, 2010 2:39 pm
Location: Montreal, Canada

Re: Importing Blogger to Wordpress - memory size error

Post by Celauran »

simonmlewis wrote:I now get this error:

[text]
Warning: Invalid argument supplied for foreach() in C:\xampp\phpMyAdmin\site\wp-content\plugins\blogger-importer\blogger-importer.php on line 227[/text]
That can probably still be worked around. Looks like it's the get author functionality that's failing. Whether it's worth pursuing further is your call.
Post Reply