Osclass Themes and Osclass Plugins

Debug Log Viewer in Osclass Backoffice: Faster Issue Diagnosis

Review application and server errors directly in backoffice to accelerate debugging and maintenance workflows.
Product Updates & Releases
26. December 2025
1 min read
19953 views
Debug Log Viewer in Osclass Backoffice: Faster Issue Diagnosis

Quick overview

Review application and server errors directly in backoffice to accelerate debugging and maintenance workflows.

What this article covers

  • Osclass debug details in backoffice

Practical notes

  • Validate changes in staging before production updates.
  • Track user impact with analytics, logs, and search performance signals.

Osclass debug details in backoffice

Osclass now contains ability to check error logs of your server/osclass directly in backoffice. To open debug details, go to your backoffice and in left sidebar navigate to "Tools > Debug/Error log":

Debug Log Viewer in Osclass Backoffice: Faster Issue Diagnosis screenshot

Once you get there, in left sidebar you will see information if debug mode(s) are enabled in your osclass (and should be disabled on production classifieds) and how to enable error logs as well. Right sidebar contains content of debug.log file that stores PHP error log output, when enabled (OSC_DEBUG_LOG is set to true in config.php).

Debug Log Viewer in Osclass Backoffice: Faster Issue Diagnosis screenshot

Pair with the configuration information page.

Frequently asked questions

Question: Where do I read Osclass debug.log in Tools, Debug/Error log?

Answer: Open oc-admin, Tools, Debug/Error log. The right pane shows debug.log when file logging is on. The left pane shows whether debug modes are enabled. Those modes should be off on a live classifieds site. An empty right pane means logging is off or the file was never created.

Question: How do I enable OSC_DEBUG_LOG in Osclass config.php?

Answer: Set OSC_DEBUG_LOG to true in config.php so PHP errors write to debug.log. Open Tools, Debug/Error log to read the file. Keep display_errors off for visitors, then turn the constant off when the issue is fixed. Copy the stack trace first so you can disable logging quickly.

Question: Why should Osclass debug stay off on a live classifieds site?

Answer: Debug output can print paths and queries on the front office and slows the site. Tools, Debug/Error log shows if debug is enabled. On production, keep it off and use OSC_DEBUG_LOG only while you copy a stack trace, then disable it. Leave display_errors off for visitors.

Question: What does the left sidebar mean on the Osclass Debug/Error log page?

Answer: The left sidebar of Tools, Debug/Error log reports which debug modes are on and how to enable file logs. The right sidebar is the debug.log body. If the right pane is empty, OSC_DEBUG_LOG is false or the file was never created. Enable logging, reproduce the error, then turn it off.

About the Author

My passion is building classifieds marketplaces, automating workflows, and turning messy data into useful products. From PHP, HTML, CSS, and JavaScript to Python, crawlers, imports, and SEO, I enjoy solving technical challenges and sharing lessons learned from real-world projects. Most ideas start with a problem, a cup of coffee, and a curiosity to see how far automation can go.
Osclass, PHP, JavaScript, CSS, Python
52 posts Publishing since 04/2018

Shopping cart
Support tickets Downloads Reviews Orders & Invoices Payments
Dashboard My profile Change password Download user data
Logout