[quote="Angus Au"]I came across problem in compiling elog 2.6.1 on solaris platform.

Is there any fix ? I can compile elog 2.6.0 successfully on solaris.[/quote]

There is a fix, we have 2.6.1 running on Solaris.

A colleague of me installed it and did mention something about having to go through the source and adapting the 
makefile. I didn't hear him speak of missing libraries though, I will ask him next week.

Greetings,

Last night we updated to 2.6.5 and now the <ENTER>-key on the "quick filter" searches won't work anymore in 
internet exporer (@windows). I have to use the <TAB>-key now to get the results.

The ENTER-key still works under firefox (Windows & linux) and opera (at least under linux, because 
opera@windows refuses to log me on .. whatever) and I would like to see it come back to internet explorer as 
well.

Regards,
Willem Koster

> Greetings,
> 
> Last night we updated to 2.6.5 and now the <ENTER>-key on the "quick filter" searches won't work anymore in 
> internet exporer (@windows). I have to use the <TAB>-key now to get the results.
> 
> The ENTER-key still works under firefox (Windows & linux) and opera (at least under linux, because 
> opera@windows refuses to log me on .. whatever) and I would like to see it come back to internet explorer as 
> well.
> 
> Regards,
> Willem Koster

ehm... funny enough the quick-filter entry used in this elog does work with IE.  

(we're using ELOG V2.6.5-1844 btw)

update: when we try just one quick-filter it works ok, when we add our second quick-filter it stops working.

Both quick-filters are tekst-searches (just like this forum only has one tekst-search quick-filter).

We suspect that this is an explorer issue and probably not something that can be solved with elog, but ... 
maybe .. who knows...



update2:

In the source we see:

    <noscript><input type="Submit" value="Search"></noscript> 

If we remove the <noscript> </noscript> tags we get a submit-button, but our problem seems to be solved. 
(obviously hacking the source-code is not our primary choice :-)

Hi there,

It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?

Cheers

Valentin

We use elog for (amongst other things) a simple change management log.  About two dozen users allowed to do updates and their email addresses are listed at the bottom of the page to allow any of them to be included on circulation for a change request.  The email addresses appear in the order that they were added (i.e. apparently random).  Is there any way to sort these, ideally by Last part of Full Name/First part of Full Name, but login name or email address would be OK?

Thanks for a great piece of software.

Steve

Hi

Thanks for elog - it's a brilliant piece of software.  I'd looked all over for open source software to log/manage change requests before discovering elog; it's so flexible that I've been able to do everything I need with it.

However, I think that I've just discovered my first undocumented 'feature'.  Attribute names containing punctuation characters (e.g. / and :) cause "Redirection limit for this URL exceeded" errors in Firefox 3.0.2 and corrupt the URL if they're used in a Quick Filter.  I often use '/' in attribute names for brevity, e.g. "Old/New Versions" but hadn't used one in a Quick Filter before.

keep up the good work.

regards

Steve

Hi

I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted.  We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence.  As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!

cheers

Steve