Skip to content
Grav 2.0 is officially stable. Read the announcement →

Muut Archive Legend

@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation

Badges

✏️ First Post 💬 Conversation Starter ❤️ Well Liked

Recent posts

  • One Page Skeleton 0.9.6 broken · 12 years ago

    Continue to occur (flushing cache between all these updates too)

  • One Page Skeleton 0.9.6 broken · 12 years ago

    and if you remove the ignore_user_abort part???

  • One Page Skeleton 0.9.6 broken · 12 years ago

    The issue still occurs.

  • One Page Skeleton 0.9.6 broken · 12 years ago

    It really is not a necessary part of the function, it was just a safe-guard for long running processes, but nothing should be running for more than the default 30 seconds anyway.

  • One Page Skeleton 0.9.6 broken · 12 years ago

    What happens if you simple remove the whole set_time_limit thing? so the whole function is: public function shutdown() { if ($this['config']->get('system.debugger.shutdown.close_con

  • One Page Skeleton 0.9.6 broken · 12 years ago

    I tried this, hopefully it is what you mean by the above: /** * Set the final content length for the page and flush the buffer * */ public function shutdown() { if ($this['config']->get('sys

  • One Page Skeleton 0.9.6 broken · 12 years ago

    I'm sure there is a restriction on the set_time_limit call. I'm going to put a couple of checks in place in the shutdown() method in the Grav.php class: if (function_exists('set_time_limit')) { @s

  • One Page Skeleton 0.9.6 broken · 12 years ago

    I can see if I can take a look...thanks for your time to to diagnose this issue. I am actually using DigitalOcean with a vps configured by ServerPilot for all hosting.

  • One Page Skeleton 0.9.6 broken · 12 years ago

    What that does is provide a powerful event that lets Grav perform actions after the page has been rendered and sent to the browser. It lets us do advanced things like tracking without impacting perfo

  • One Page Skeleton 0.9.6 broken · 12 years ago

    That seems to have fixed it...but why would that be enabled in the version we can download on getgrav.org? (just for curiosity/learning sake).