Re: (How) can I hide columns in List view?, posted by T. Ribbrock on Thu Oct 23 11:45:51 2008
|
T. Ribbrock wrote:
[...]
One thing I don't understand for example is how does elog decide in List view which entry sets the condition? |
|
Select -> Edit wipes dates, posted by T. Ribbrock on Mon Oct 27 12:42:47 2008
|
I just ran into the following bug:
I have a logbook where entries have several attributes, among which several dates. All of these are set to "Type <attr> = date".
If I use the "Select" action, tag several entries and subsequently chose "Edit", the values of all date attributes are wiped. All other |
Re: (How) can I hide columns in List view?, posted by T. Ribbrock on Thu Oct 30 09:44:25 2008
|
Thanks for the response! BTW: I did get a notification - but thanks for the "personal heads-up"!
|
Re: (How) can I hide columns in List view?, posted by T. Ribbrock on Thu Oct 30 11:05:11 2008
|
Stefan Ritt wrote:
[...] |
Re: Installation problems, posted by T. Ribbrock on Wed Nov 5 11:52:12 2008 
|
> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> >
|
|
Re: Select -> Edit wipes dates, posted by T. Ribbrock on Thu Nov 27 11:36:53 2008
|
Stefan Ritt wrote:
This problem has been fixed in revision 2.7.5-2143. Please upgrade. |
Re: Installation problems, posted by T. Ribbrock on Thu Nov 27 11:47:34 2008
|
> The problem is not putting this into the "conrib" area, but supporting it. Since I don't have a Debian system,
> may I suggest that you put it yourself into the elog:Contributions/ logbook. If people then get problems in the
> future, they can contact you directly ;-)
|
Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 12:12:37 2009
|
For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of
the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running
2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group |