Ticket modified by Ralf Becker at 2010/12/04 01:53
Tracking System: Bugs
Category: Admin
Version: Trunk
Status: Pending
Resolution: None
Completed: 0%
Priority: 1 - lowest
Created By: Carlos Lorenzo Matés
Assigned to: not assigned
Summary: #446 - Error in the view error log application
The vier error log shows no registers, but it say showing 1 to 15 of 235424 records
if i edit the table format the only thing i can see is a bunch of blank fields and no option to select wich fields i want to see.
Comment by Ralf Becker at 2010/12/04 01:53:
Dear EGroupware user,
thanks for reporting bugs back to egroupware.org.
With the new release of EGroupware 1.8.001 we also fixed many bugs. So we kindly ask you to recheck your bug reports against the new version.
If you do not respond within the next 14 days, we assume the bug no longer exist and your report will be closed automatically.
Thanks for your understanding
Ralf Becker
Stylite GmbH
Comment by Carlos Lorenzo Matés at 2008/11/18 17:10:
So, if this has not use, what I would expect is that this option do not appear in the admin menu, and this two tables to be empty and to not grow in time 
Comment by Ralf Becker at 2008/11/17 04:45:
Hi Carlos,
what do you expect to see in that log?
As far as I know, all current code logs into the Apache error_log.
Ralf
Comment by Carlos Lorenzo Matés at 2008/10/22 17:52:
Still confirmed in 1.6rc2
Comment by Simo Kivimäki at 2008/10/16 20:26:
I can repeat this with 1.6.rc1.
Comment by Ralf Becker at 2008/10/15 21:49:
Dear bug reporter,
we finished the first release candidate for the upcoming 1.6 release 
Therefore we kindly ask for your participation in fixing the remaining bugs. Please check if your reported bug is still present in the release candidate (report as 1.6.rc1) OR a newer svn checkout (report as Trunk).
If the bug still exists in 1.6.rc1 or Trunk, please update the version accordingly and indicate it in your comment.
If the bug does not exist in 1.6, but of cause still in 1.4, you can reopen it with version 1.4 - thought we probably don’t have the resources to fix non-security-critical bugs in 1.4.
If you don’t update your bug, we assume the issue no longer exists and the bug will be closed automatic after 14 days.
Thanks for your understanding
Ralf
eGroupware administrator
Comment by Carlos Lorenzo Matés at 2008/04/24 19:55:
Confirmed in 1.4.004 + svn updates
Comment by Simo Kivimäki at 2007/10/09 16:22:
I can repeat this bug with eGroupWare 1.4.002. Database is PostgreSQL and the log messages are not saved there correctly.
Attachments include output of “select * from egw_log_msg” and “select * from egw_log” where is some errors from unsuccessful LDAP login attempts.
Comment by Flávio Henrique at 2007/09/27 18:19:
It works for me, sorry.
Flávio Henrique
WinXP Pro
Php 5.2.3
MySQL 5.0.37
Comment by Carlos Lorenzo Matés at 2007/09/27 16:46:
Still the same problem.
Has this option worked for anybody?
Comment by Ralf Becker at 2007/09/25 06:57:
We just released the new 1.4.002 with many bug fixes and improvements. It fixes many problems reported over the last weeks.
WE NEED YOUR HELP: can you please verify your bugs against the new version. It’s only a handful bugs per submitter, but a few hundred per developer.
Please respond / comment to your bug, if the problem is NOT fixed in 1.4.002. If you don’t respond the bug will be closed automatically in 2 weeks.
Please note: we can NOT fix bugs in 1.4.001 (only in new releases) and the old 1.2 versions are no longer supported.
Thanks for your understanding and help
The eGroupWare developers
Comment by Carlos Lorenzo Matés at 2007/05/15 05:43:
Confirmed in 1.4
i just oppened a new bug, because didnt notice this,im going to close the new bug now
linked entries:
http://www.egroupware.org/egroupware/index.php?menuaction=tracker.tracker_ui.edit&tr_id=446&no_popup=1