Store
Community Documentation

v3 Knowledgebase

Basics of Reading a Debug Message

This is just a basic article for how to read a debug message. There are far too many variables in regards to debug but for new members to get an idea of what they are seeing when they enable debug:

AdminCP >> Settings >> Manage Settings >> Debug at level 1 is usually sufficient to check for errors.

** Note to first check your server for the dev.sett.php file that can sometimes be left behind in include/setting/ and rename or remove that so you can see errors as that will disable debug in Admin and is not recommended to have on a live site **

Once you enable debug, if there are issues on your site, you will see an error message on the various pages of your site.

I will copy now an error seen after a member did not install an add on properly and show you how to see what the issue is in order to know who to contact to fix it if you cannot:

Quote:

User Error: Failed to load component: module/pages/include/component/block/tm-pagephotos/tm-pagephotos.class.php - include/library/phpfox/error/error.class.php (91)


Failed to load component

This is saying that the script cannot load a component that it is being asked to load. Most likely, the add on was not installed to tell the script that this component exists or there was a typo when creating the block for this as the instructions for this add on say to create a certain block. So now we need to see what add on we are dealing with in order to get assistance.

module/pages/include/component/block/tm-pagephotos/tm-pagephotos.class.php


In this, we see that the path is showing us what add on was not installed properly, tm-pagephotos . Because the instructions for this add on have the member create the block, we can guess that the files were not loaded to the site properly (perhaps the upload folder was loaded) and so the script cannot find that file it was requested to find. It could also be a typo in the block created. Either way, the member would need to seek the assistance of the creator of the add on in order to fix the issue.

Another basic example of a debug message and how to see what add on is causing issues:
Quote:

Notice: Undefined variable: src in /home/site/public_html/module/modsfox/include/service/styles.class.php on line 64

Notice: Undefined variable: show in /home/site/public_html/module/modsfox/include/service/styles.class.php on line 64

Notice: Undefined variable: sMoodsTag in /home/site/public_html/module/modsfox/include/service/styles.class.php on line 64


In the above, we see an Undefined variable in the add on. This is something the developer needs to fix but, what developer?

Well, we see this path:

module/modsfox

the modsfox is the module that has the problem. What we do now is recall which of our add ons is called modsfox and contact that developer to fix the issue.

This article is not to point out any flaws in any developer's products. It is just to help you learn how to basically read a debug error message so you know who to contact if you have issues.

If you get an error like this:

phpfox_user table crashed or phpfox_log_session crashed these are saying that your database tables are crashed and need to be repaired. Your server technicians can do that for you if you are not able to do it yourself. Our support can also fix this.

Sometimes debug will show a lot of errors listing Cache. A good thing to do is to clear your cache on the server in file/cache and leave the index.html file in there. This will remove any old things that could still be haunting your site and causing issues and will pull fresh files from the Database for the site to use. A lot of times, debug errors will go away and a site will return to normal operation after clearing cache on the server.