0

Finding it hard to debug my problem, I am getting a blank page when searching for a product.

When I check my system.log there's nothing there explaining the error, could someone let me know where I would start debugging this problem!

Sorry if the question is too broad can't think how I would expand it as I can't debug it with no error message to work off!

EDIT

Sorry I should of mentioned, yes I have display_errors on and developer debugging and logging etc on.

11
  • Can you turn on the display errors in the index? And developer mode too if possible Commented Oct 8, 2015 at 8:37
  • Yes, ensure the logs are enabled. Then I suggest you check the server error log (not Magento logs). Commented Oct 8, 2015 at 8:41
  • system.log empty and blank page sounds like memory_limit imho. Can you check your apache error log? Commented Oct 8, 2015 at 8:41
  • page is working again now btw. As simonthesorcerer says, it could be a memory_limit problem or a disk space issue too. Commented Oct 8, 2015 at 8:53
  • weird, and yeh logs enabled/ini_dis errors on for deving anyway Commented Oct 8, 2015 at 8:58

1 Answer 1

2

Firstly make sure that logging is on in the admin under System>Configuration>Developer, as the other commentators said.

It is a live environment so you could, pro-tem add error reporting to your index.php page, but make sure you remove it once the issue is resolved. Ideally you could debug the problem on a local environment.

In the [site-root] index.php page you can do the following:

error_reporting(E_ALL | E_STRICT);
ini_set('error_reporting', E_ERROR);

and possibly

ini_set('display_errors', 1);

(this may be commented out)

Another thing you can do is a add a register_shutdown_function/ e.g.

register_shutdown_function("fatal_handler");
function fatal_handler() {
    $error = error_get_last();
    echo "<pre>";
    print_r($error);
    echo "</pre>";
}

but be warned this will stop the "suppress error" operators (see function calls with @ in the front) so may raise additional problems and should not be run on a live environment. A common surprise issue is the reporting of an error in mage/core/Translate.php . Another is that Ajax calls may stop working (as errors are added to output, breaking the formatting). So make sure you do not leave this on.

Of course there is the possibility that you are seeing a cached "blank" page in your browser when it is actually working. Try clearing your cache or forcing a hard reload on the page. You can achieve this in Chrome by opening your dev tools and right clicking on the refresh button and choosing "clear cache and hard reload", or pressing shift-F5. Alternatively you can open the page in incognito mode which should ignore the cache.

1
  • Already had all this Commented Oct 8, 2015 at 8:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.