Bug #57217
closed
Module belog not displaying content
0%
Description
We're using the current master branch of 6.2 already for some projects and the belog module is not working for me or my colleagues since two months ago. In Web Inspector I see that some HTML gets loaded correctly, but nothing happens then, the screen just stays blank. I don't have any errors in the PHP log, also not in sys_log table.
Updated by Georg Ringer over 10 years ago
- Status changed from New to Needs Feedback
some more details please. using windows? set
<IfModule mpm_winnt_module> ThreadStackSize 8388608 </IfModule>
in
httpd.conf.
Updated by Thomas Off over 10 years ago
Server is Debian 7 using Apache and PHP 5.4 as Apache module; clients tested were Chrome, Safari and Firefox under Mac OS X, IE under Win 7.
When I click on the Log module menu entry in the left frame of the backend, the spinning load indicator appears for a short while, then disappears and leaves a blank page. In Web Inspector I don't see any errors or failed requests, my server log is clean as well. I've already remove all entries from table sys_log and reset my user preference, but nothing fixed the problem.
Updated by Markus Klein over 10 years ago
- Status changed from Needs Feedback to New
Please also clear all caches (install tool) and your browser cache
Updated by Thomas Off over 10 years ago
I just updated my Git tree to latest commit, cleaned the browser and all TYPO3 caches, but nothing helped, the log module stays blank. I'll give it a try and start from a fresh install of the latest RC2 and will report back with the results.
Updated by Thomas Off over 10 years ago
After reviewing this issue some more, I found out that the log module doesn't work anywhere I upgraded from 6.1 to 6.2 – I'll dig into this deeper to get a solution and post it here afterwards.
Updated by Thomas Off over 10 years ago
After some more research we have found the reason: it's the "view" extension! I'll try to investigate, how exactly it prevents the log module from working and post the results here again.
Updated by Thomas Off over 10 years ago
We didn't find out exactly what's causing the problem, but think that it's more a bug in the view extension than in the core, so this ticket should IMHO be closed.
Updated by Markus Klein over 10 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
6.2.0)
Thanks for reporting!