Re: Suggestion additional ElCodes, posted by T. Ribbrock on Wed Jan 25 12:31:14 2006
|
[quote="Stefan Ritt"]
Yes, I missed tables myself already. The headings I just put into the current SVN version (see this forum for how it works).
[/quote]
|
Numbered lists get closed by </ul>, posted by T. Ribbrock on Mon Jan 30 16:26:08 2006
|
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):
[LIST]
|
Upgrade to 2.6.4 broke quick search, posted by T. Ribbrock on Tue Mar 6 16:59:13 2007
|
Hi!
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I |
Re: Upgrade to 2.6.4 broke quick search, posted by T. Ribbrock on Tue Mar 6 17:03:43 2007
|
[quote="T. Ribbrock"]
[...]
I just went from 2.6.1 to 2.6.4 and since the upgrade, the quick search drop-down menus no longer work. I can select an attribute, but when I do so, I |
|
Using the command line tool to edit, posted by T. Ribbrock on Thu Aug 7 10:12:25 2008
|
I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping to be able to do this using the "elog" command
line tool. Adding a new entry works fine, as does "replying" to an existing entry. The only thing I cannot get to work is editing an existing entry. All
entries ahve several attributes and I intend not to use the "message" itself. I tried the following (on the machine this elogd is running on): |
|
Re: Using the command line tool to edit, posted by T. Ribbrock on Fri Aug 8 14:50:56 2008
|
[quote="Yoshio Imai"][quote=T. Ribbrock][B]NOTE:[/B] I found that this does [i]not[/i] work if LOGBOOK has any spaces in it - I would get error messages
where the logbook was not found.[/quote]
|
|
Re: Using the command line tool to edit, posted by T. Ribbrock on Mon Aug 11 15:14:40 2008
|
Stefan Ritt wrote:
I fixed two things: |
Options selections wipes locked date entry, posted by T. Ribbrock on Mon Oct 13 15:24:29 2008 
|
I have two logbooks running, one for current accounts and one for non-active ones. The idea is to move an entry from one logbook to the other once an
account becomes non-active. Both logbooks share some attributes (e.g. the name of the account, its creation date, ...), but both also have some uniqe attributes.
While I was playing with this set-up, I ran into a problem: |