ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67339
|
Mon Sep 17 13:42:50 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.9.2-2473 | Mysterious Emboldened lines in threaded (collapsed) mode | I upgraded my system, including the version of Firefox.
I normally view the topic in Threaded Collapsed mode, right click on the entry I want to reply to, to open a new
Tab. However, I made a mistake an opened a new Window, as the two 'open' modes in Firefox swapped around.
But no worry, I thought, made my reply as usual.
However, when refreshing the topic afterwards, seemingly randomly distributed throughout the topic were
additional lines, with the latest entry showing up emboldened (but not as a clickable link), and the only
difference being the ID number which showed as 0 (zero).
Deleting the reply only caused the previous reply to show up randomly etc.
In effect, the latest entry is (randomly?) scattered throughout the topic - even in between entries older than
any in that thread, so it's not individial entries in that thread showing up.
The only way to get rid of it was to erase the whole directory, and re-install from backup (which, as it was the
first entry since the new installation, wasn't painful). It's been fine since - but only so long as I open a
thread in a new tab, and not in a new Window.
I guess the real question is just what is added to some file - perhaps the .cfg file? - that using a separate
window causes this behavioir? Any whay only as a new window, and given how elog is supposed to work on many
computers, why on this stand-alone computer running two sets of the same browser?
It happened once before at the end of last year during a regression backwards owing to the newer computer
failing and turning back to an older one with older OS and older firefox, where I did the same thing (in
reverse). As I didn't investigate at that time, I still have the mystery line showing up in that topic.
Sorry this is a bit rambling, but its very hard to describe! |
67338
|
Mon Sep 17 09:16:38 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 2.9.2 | Re: HTML editor |
Josef Uher wrote: |
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum. |
67337
|
Sun Sep 16 21:14:12 2012 |
| Josef Uher | josef.uher@gmail.com | Bug report | Mac OSX | 2.9.2 | Crash with long image names | Hi All,
I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full view with attachments visible. If I shorten the name all is fine.
The crash report screenshot is attached. It looks like a too small buffer (?).

|
Attachment 1: Screen_Shot.png
|
|
67336
|
Sun Sep 16 18:40:06 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | HTML editor | Hi All,
maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?
Thanks a lot for advice. |
67335
|
Fri Sep 14 17:59:44 2012 |
| Louis de Leseleuc | louis.deleseleuc@nrc-cnrc.gc.ca | Bug report | Linux | 2.9.2-2455 | ELOG crashes when editing threads | Hi,
I am experiencing repeated crashing of the elog daemon.
If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry.
When I do so then press the Edit button, the server crashes.
I have to manually restart it. Syslog shows no error.
This does not happen under Summary or Full view.
Running Ubuntu 12.04, ELOG 2.9.2-2455
I can provide my elog.cfg if necessary.
Cheers!
Louis
P.S. i just crashed the forums ELOG following those same steps!! Sorry!! At least it was restarted in no time. |
67334
|
Wed Sep 12 10:50:40 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9 | Re: Type <attribute> = Date - Issue |
Garret Delaronde wrote: |
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
The problem is, that the existing entries have a string content for this specific attribute.
An attribute with a "date" type content should contain a integer number, which represents the seconds of the epoch (starting with zero on 1-Jan-1970 at 00:00:00).
What you need to do is writing a script that reads all *a.log files in the logbook directory and converts lines of the type:
<attribute>: <text>
to lines like
<attribute>: $(date -d "<text>" +%s)
Unfortunately elog does not provide you with such a tool.
But since you have to write it now anyway now, you could submit your code to this forum 
Andreas |
67333
|
Mon Sep 10 17:18:03 2012 |
| Garret Delaronde | garret.delaronde@gmail.com | Bug report | Windows | 2.9 | Re: Type <attribute> = Date - Issue |
David Pilgram wrote: |
Garret Delaronde wrote: |
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
Hi Garret,
Why cannot you just use $entry time ? It uses the date that the entry was made which appears as the first line of every elog entry -
[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]
MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
You can use 'Time format = ' to get the date to display in the format you like. You will see I have posted an issue about 'Date format = '. I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread. I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.
Of course I may have mis-understood your requirements.
|
Tried using the Time format setting, however I only want the time to be selected, so when i enter the datetime type it shows the date and time.
If there was a way to just have the time to be drop down menus vs the date and time all together, I would find that helpful.
As for the "$entry time" suggestion, it only serves to log the exact time the entry was made into elog. Where as I want it to be manually set.
In this example we've created an sql script to pull information from an oracle database, which then creates an elog entry.
We have multiple fields which are populated and locked so only admin can edit them.
Our contractor then edits the entry with a date / time / location, and a few other things.
the Date and Time are separate attributes. We'd prefer to keep it like that just because of the other scripts that run on the elog entries, (pulls day by day reports and formats and calculates summaries in excel automatically).
Any other suggestions would be helpful.
Thanks for your reply. |
67332
|
Fri Sep 7 19:08:27 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Windows | 2.9 | Re: Type <attribute> = Date - Issue |
Garret Delaronde wrote: |
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
Hi Garret,
Why cannot you just use $entry time ? It uses the date that the entry was made which appears as the first line of every elog entry -
[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]
MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
You can use 'Time format = ' to get the date to display in the format you like. You will see I have posted an issue about 'Date format = '. I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread. I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.
Of course I may have mis-understood your requirements.
|
|