Support » Plugin: WP Pipes » Memory consumption problem

  • Recently, I noticed the following failure repeating periodically:

    PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 151341317 bytes) in /home/helices/public_html/wp-content/plugins/wp-pipes/plugins/processors/get_fulltext/readability.php on line 39

    Other than allocating more and more memory, how can I reduce required memory for WPPipes?

    Please, advise. Thank you.

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Please check out this article to reduce database size; it’s a very helpful site:




    What does this have to do with my memory consumption issue?

    Please, advise. Thank you.

    ~ Mike

    Posts are saved in the database. Different post types are posts, pages, images, custom css and regular posts. Everytime you’ve updated a post a new copy of it is saved in the database(also autosave post feature creates new post copy).

    Also you’d reduce image size using some good plugin such as

    Hope I could be of some help!

    All the best,

    Saurabh 🙂

    PS: Your webhost will do a better job at explaining it


    Although, what you say is true, it is non sequitur.

    This plugin writes every post one and only one time. So, “disabling revisions” cannot possibly apply to my situation.

    ~ Mike


    With the message you showed, I think you are using Auto Fulltext feature of Get Fulltext processor, right? That is a feature which makes WPPipes auto detect and pull content from original news base on the standard HTML structure. However, not all sources use standard HTML structure, so it could cause problems while the pipe grabbing.

    As my experience, I use HTML Parser processor with Parser Code feature instead of. And follow me, that is the best way to pick up correct content.


    Since HTML Parser processor is a pay addon, how does this work?

    What does this addon processor do that the default WPPipes plugin will not do?

    I don’t mind paying, if I know what I’m getting …


    That processor add-on is an advanced feature from WPPipes’s author. It has Parse Code feature which I think it is very powerful for you detecting and pulling content correctly as you want by yourself instead of using auto feature of Get Fulltext processor.

    Please tell me the RSS feed which you want to pull content, I will try to give you the difference!

    FYI: I am only the user of WPPipes but I could say I am a professional user :”)!

    Currently, I have eight (8) different pipes, each of which aggregates news from many different RSS feeds. One (1) pipe aggregates feeds from the following? 

    How would this addon plugin work in my situation?

    Yes, I see the differences.

    [1] Is this the default setting for HTML parser addon?

    [2] Will this work well for all dozens of RSS feeds in one Pipe?

    [3] Does HTML parser addon need to be configured separately for every RSS feed?

    Please, advise. Thank you.

    Maybe these information will be helpful for you:

    1. Parser Code feature works base on the HTML structure of source pages. So you will need to have a bit knowledge about HTML. Because different sources have different HTML structure, so with each specific source, you will have a specific way of using Parser Code.

    2. You should use Parser feature with RSS feed if that feed only includes news from 1 source. Other way, the feeds which include news from various sources, you could not use this feature, for example: Google News feeds.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Memory consumption problem’ is closed to new replies.