Fatal Error – Allowed Memory Size

  • Resolved Tom Kraeutler

    (@tomkraeutler)


    8 years, 5 months ago

    Hello, I tested this plugin on our Staging site and it crashed displaying the following error:

    Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 32 bytes) in /nas/content/staging/moneypit/wp-includes/taxonomy.php on line 1401

    See screenshot here: https://cl.ly/132Q2v0a1A02

    We have a large volume of posts (over 9,000) so not sure if that impacts this but would appreciate any feedback. We really only need posts matching a specific category but I do not see an option to limit the export to anything other than post type.

    Also, it did export a zip file but that file did not appear to contain any useable data.
    See this screenshot: https://cl.ly/0x2v0n1u2g0I

    Thanks for your help!

    • This topic was modified 8 years, 5 months ago by Tom Kraeutler.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Tom Kraeutler

    (@tomkraeutler)

    8 years, 5 months ago

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

    Plugin Author Atlas Gondal

    (@atlas_gondal)

    8 years, 5 months ago

    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!

    Plugin Author Atlas Gondal

    (@atlas_gondal)

    8 years, 4 months ago

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

    Thread Starter Tom Kraeutler

    (@tomkraeutler)

    8 years, 3 months ago

    @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 8 years, 3 months ago by Tom Kraeutler.
    Plugin Author Atlas Gondal

    (@atlas_gondal)

    8 years, 3 months ago

    @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.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Fatal Error – Allowed Memory Size’ is closed to new replies.