As a newcomer to OroCrm, I recently installed and configured it on my DEV environment using the app_dev.php entry point.
After setting up OroCrm, I immediately noticed the Symfony2 profiler bar appearing at the bottom of the interface. While this was a helpful feature, I encountered a problem where the profiler did not update when navigating through different pages, leading to a 404 error popup.
To resolve this issue, I made a modification in web/bundles/oronavigation/js/navigation.js (line 544) by changing:
var url = entryPoint + '/_wdt/' + debugBarToken;
to:
if ('/' === entryPoint.charAt(entryPoint.length - 1)) {
var url = entryPoint + '_wdt/' + debugBarToken;
}
else {
var url = entryPoint + '/_wdt/' + debugBarToken;
}
This adjustment successfully resolved the issue for me, as now the profiler updates with each page request. I am curious to hear other perspectives on this matter and explore alternative solutions that were effective for others.
UPDATE: In OroCrm 1.1.0, there are no errors reported, but the debugbar remains locked on the DashboardController even when switching sections or navigating to different pages. By applying the code update mentioned above, the debugbar now accurately displays the current request status instead of being stuck on the DashboardController.