Hi,

Is it possible to disable the Previewbutton?

Regards
Ulf Olsson

 Nope.

 Is it possible for you to implement this function in a future version of ELOG?

 If there is a good reason for that ...

The reason for doing this is that the GUI will be cleaner and easier for the users to understand.
If it´s possible to disable functions that you don´t need in a customized ELOG it would be easier to explain how to work with it.  

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!

> I upgraded my system, including the version of Firefox.
> [...]
> Sorry this is a bit rambling, but its very hard to describe!

A picture can say more than thousand words.
Can you reproduce this with a simple configuration?
If yes, can you attach the configuration, the *a.log files,
a description of what firefox version you're using and please:
some screenshots of "before" and "after"?

Thanks!
Andreas

> > I upgraded my system, including the version of Firefox.
> > [...]
> > Sorry this is a bit rambling, but its very hard to describe!
> 
> A picture can say more than thousand words.
> Can you reproduce this with a simple configuration?
> If yes, can you attach the configuration, the *a.log files,
> a description of what firefox version you're using and please:
> some screenshots of "before" and "after"?
> 
> Thanks!
> Andreas
That's odd, I cannot reproduce the problem today - except on the topic [logbook] it already exists on.
Yet nothing has changed.  
I've looked for hidden files, hidden control codes in the *a.log files...  this one had better be put on the
back burner until I can find a way to reproduce it (!).

 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.

 Hi Andreas, thank you for your reply. I have already found out that the problem on Mac was that I moved the cfg file to some other folder which did not contain the resources and scripts. I used the "-s" switch and now it works nicely. However, now I try to do the same thing on Windows and even the "-s" switch does not help (the default encodings etc. are set in the cfg file). I compiled the elog on Mac, but I used the installation package on Windows.

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 (?).

 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.

 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.

I don't think there is a good secure way so far, but would like to have your opinion. 

If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

 Thanks, that is good option. 

 Is there a way to set user permission based on certain attribute? can Allow command = <user list> based on attribute?
for example, say type home, user1 can read, user2 can write, user3 can not access type home, but can access type work. 

In short, is access control available when I use type to get functionality of separate logbooks? If so, how is this access control done? 

Actually I never tried that. Using conditional attributes, you could try that out, but no guarantee that it works. Like

Options type = home{1}, work{2}

{1}Login user = you, me

{2}Login user = me, other

You could play with "login user", "Allow command" and "Deny command".

/Stefan 

 Thanks for reply Stefan. 

I tried it, didnt work. I think its expected it didn't work though, or maybe I didn't try it right. 
==============
[logbook1]
Login user = user1
Options Type = Home{1}, Work{2}
{1} Login user = user2

This will make user2 unable to login logbook1 at all

============
[logbook1]
Login user = user1, user2
Options Type = Home{1}, Work{2}
{1} Login user = user1
{2} Login user = user2

user1 can login, can search Work type entries, create new entry with Work type.  

==============

[logbook1]
Login user = user1, user2
Options Type = Home{1}, Work{2}
{1} Deny New = user1

user1 can still create entries for Home type. I think it's because when user1 login, command New is available for user1, so when user1 click on New, doesn't matter what type user1 choose, submit button is available. If I have Deny New = user1 under logbook1, New is not available, that means user1 can't create entry for Work type either. 

===============

seems to me under current code, access control has to be done based on logbook, not attribute.  Do you agree?

if that's the case, we may have a lot of logbook because of access control we want to implement. So there is another question:
selection page show all logbooks. Is there a way to make selection page and tabs show logbooks based on user access?
For example, we have 20 logbooks, user1 has acces to 3, when user1 login, selection page only shows that 3 logbooks for user1, and only 3 tabs for user1. 

 
I thought about using group to get logbooks more organized, however I will still face the situation that one group may have 20 logbooks. 

Or what would you do to handle this situation? (I asked selection page question earlier in another entry). Maybe we should discuss on that entry? Message ID: 67319 

Thanks again. 

 

Hi,

I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats

Extract from my elog.cfg file:


Time format = %a %d %b %y
Date format = %d %b
Thread display = $Ticket: $System, $entry time. ($message id). $status
Preset text = [$date]
Prepend on reply = [$date] \n

I can point to places in the syntax doc where each of these lines are given.

As for the results, the thread display is (for example):

T00001: Computer, Wed 29 Aug 12. (1). Problem

However, what I get at the top of the text box in starting a new entry or replying to a previous one is

[Wed 29 Aug 12]

whereas I expected to get

[29 Aug]

Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference

I cannot see where I'm going wrong.  

TIA 

David.

OK, I see that $date can work in a different way; if the Thread display uses $date,
then the present timestamp is substituted into the thread display line, rather than the 
date that the entry is entered.  So, for example, in a whole list of entry and replies, the present
date shows on each entry of the thread.  However, the format is still that as defined by
'Time format' rather than 'Date format'.

If nothing else, I cannot really see the point of the 'Date format =' in the way that this all works.

> Hi,
> 
> I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats
> 
> Extract from my elog.cfg file:
> 
> 
> Time format = %a %d %b %y
> Date format = %d %b
> Thread display = $Ticket: $System, $entry time. ($message id). $status
> Preset text = [$date]
> Prepend on reply = [$date] \n
> 
> I can point to places in the syntax doc where each of these lines are given.
> 
> As for the results, the thread display is (for example):
> 
> T00001: Computer, Wed 29 Aug 12. (1). Problem
> 
> However, what I get at the top of the text box in starting a new entry or replying to a previous one is
> 
> [Wed 29 Aug 12]
> 
> whereas I expected to get
> 
> [29 Aug]
> 
> Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference
> 
> I cannot see where I'm going wrong.  
> 
> TIA 
> 
> David.