@megabiteas Sorry to hear about your issue, do you have an example link of the blank page so that we can check?
Unfortunately no, since it is our client´s pages we need to fix the issues immediately when they occur – so as of right now we dont have any examples.
@megabiteas I was just checking the website now, and this page seems to have the issue: https://www.glassfiber.no/marked/
The could be a PHP error that stops the page from being built, but the page still gets cached, even though not complete.
Could you check the PHP error logs to see if anything was reported?
Marc
Hey, thanks for getting back to me – it appears that this page has that issue yes. I have the error log, but it is a bit hard to understand for me – any way of sending it to you?
You can use https://pastebin.com/ to share its contents.
If you’d rather not post them here, you can send the link via this form on our website.
Marc.
Thanks – Ive sent it with the form 🙂
Hi @megabiteas
Thanks. I didn’t find anything helpful in the logs.
Is the cache preloader enabled?
Marc.
Can enabling that feature cause these problems? Had this issue again yesterday with another big client – it´s critical that we figure out what is causing this so that we can prevent it from happening.
It shouldn’t be the case, but you may want to try disabling it.
The reason being that the preloader will effectively visit all the pages one after the next, which could in some cases cause the server to run out of resources. This could end up breaking a page while being visited.
The issue could be somewhere else: the page caching saves the output of a page, and if something else interrupts the process, it will be saved with missing parts.
So this would be hard to notice without cacheing, but with cacheing the error is effectively saved in the cache.
