My question is what are some alternative methods of determining or tracing the source of an error in Joomla when the source of error isn't shown by normal debugging means? By normal debug methods, I mean the ones I have tried.

I am trying to determine the source of the error 0 Class 'ContentHelperRoute' not found on some components (mostly Search component and DJ classfieds in Joomla 3.6.5). I've found that the problem goes away after a page refresh but it appears again very often.

I tried:

  • enabling debug switch in configuration
  • set PHP error level to max
  • search error in server log but the resulting debug information doesn't allow me to pinpoint what is causing the error.

  • I've looked at the pointed solution: PHP Fatal error: Class 'ContentHelperRoute' not found but it is not the same because in my case as I have no info about the source of the error. I understand that there is an error but I cannot find where it occurs.

Are there any other ways to trace errors under Joomla? I appreciate any suggestions.

Screen: enter image description here

  • Is this the error message you get? Where do you get it? What do you see in the screen? Is it possible that your issue is this one PHP Fatal Error Class contentHelperRoute Not Found and the suggested solution the fix?
    – FFrewin
    Commented Jan 31, 2017 at 20:29
  • 1
    Possible duplicate of PHP Fatal error: Class 'ContentHelperRoute' not found
    – FFrewin
    Commented Jan 31, 2017 at 20:32
  • @FFrewin - in my case there is no way to determine where problem occurs. Onlu Class not found. There is no additional info in debug panel, no php error, no single line in server log. Problem sometimes occurs sometimes not, it occurs in many components.
    – Barto
    Commented Feb 1, 2017 at 9:13
  • My main question is not how to solve this error but: is there any other way to debug Joomla app?
    – Barto
    Commented Feb 1, 2017 at 9:28
  • 1
    It may be that something changes the error_reporting in your configuration / site, e.g. your hosting provider may have disabled error logging
    – FFrewin
    Commented Feb 1, 2017 at 9:48

2 Answers 2


Per FFrewin:

To fix this bug, you can edit the mod_articles_categories.php and add this line after the defined('_JEXEC') or die;:

JLoader::register('ContentHelperRoute', JPATH_SITE . '/components/com_content/helpers/route.php

Reference: https://joomla.stackexchange.com/a/18849/5638


I found only one solution. I switched off one component/theme/module after another and found that problem was with the code in mod_articles_category override in template. I don't know exactly why but it was not necessary so I removed it:

if ($item->parent_title!='ROOT') $nadkategoria='<a href="' . JRoute::_(ContentHelperRoute::getCategoryRoute($item->parent_id)) . '">' . $item->parent_title . '</a>';?>

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.