Fatal Error – Allowed Memory Size

Also, it did export a zip file but the file did not contain usable data. See this screenshot: https://cl.ly/0x2v0n1u2g0I

Hi Tom,

Thanks for creating ticket, I’ll be happy to assist you! ??

9000 is not a big number but it could be an issue on limited hosting packages. So, there are two possible solutions for you:

• Change memory limit
• Export posts separately

Change Memory Limit:
Check these for changing memory limit Link 1 Link 2

Export posts separately:
As title says export posts separately like in the first run, select title, urls and categories for pages only and in the second run; all data for posts and in the third run …. so on …

I’m pretty sure, one of these solution will work for you and if it doesn’t work then report back!

@tomkraeutler now you can specify post limit before extraction to bypass memory error. You would just need to export in multiple chunks…

@atlas_gondal Thanks for this update. I was able to extract using the range option but have a question. If I set the first export range set from, for example 1 to 2500, and then set the next export range set for 2501 to 5000, would I be assured that there would be no duplication of URL’s between set 1 and set 2? It’s not clear where that “range” number pulls from. You can assume that for this example, all other selections would be identical for both exports (both exporting same content type, etc.g

Also, I have a suggestion for your next update. it would be most helpful if we could also select a category or set of categories for the export. I see that we can select a specific user or set of users, but for us an expert by category would be very useful.

• This reply was modified 6 years, 10 months ago by Tom Kraeutler.

@tomkraeutler you are right, there won’t be any duplication if you export 1-2500 and then 2501-5000 and so on…

Lemme know if you still have any confusion.

Thanks for suggestion, I’ll consider this in future updates.