Warning: You are browsing the documentation from version 4 to 10 of Pimcore. Please visit https://pimcore.com/docs/platform/ for the latest versions of Pimcore.

Version:

Debugging Pimcore

In this chapter, a few insights, tips and tricks for debugging Pimcore are shown. This should give you a head start when developing with Pimcore.

Server-Side Debugging

For server side debugging, standard php and Symfony framework debugging tools like the following can be used.

Reading log files as described here
Using Symfony profiler console depending on the active environment. Details see Symfony docs
Using Xdebug and a proper IDE for stepwise debugging, more information see Xdebug docs

Client-Side Debugging

For proper debugging of Pimcore backend UI activate the DEV-Mode in system settings. By doing so, all javascript files are delivered uncompressed and commented. Thus debugging tools provided by browsers (like actual error lines, debugger, stack trace, etc.) can be used.

HTTP Headers

Pimcore might add following headers to its responses to provide additional debug information, especially concerning full page cache:

If response is delivered directly from full page cache:

X-Pimcore-Output-Cache-Tag:output_<SOME_HASH>: Cache tag of delivered information.
X-Pimcore-Cache-Date:<CACHE_DATE>: Date when information was stored to cache.

If response could be delivered from full page cache, but is not:

X-Pimcore-Output-Cache-Disable-Reason:<SOME REASON>: Describes reason why response is not delivered directly from full page cache. Reasons can be in debug mode, backend user is logged in, exclude path patter in system-settings matches, exclude cookie in system-setings matches, etc.

One additional header to identify that response is sent by Pimcore.

X-Powered-By:pimcore: Added to every request.