problem with boolean attributes, posted by Heiko Scheit on Fri Aug 1 13:18:42 2003 
|
Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached. |
|
width of the textarea is too large (after reply), posted by Heiko Scheit on Mon Aug 4 14:02:52 2003
|
The width of the textarea after pressing reply is too large.
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
number of characters in the text to be the width of the longest line.
To search for '\n' instead should solve the problem. Please find the
diff output below.
$ diff -c elogd.c elogd.c~
*** elogd.c Mon Aug 4 13:57:35 2003
--- elogd.c~ Fri Aug 1 13:13:09 2003
***************
*** 6028,6035 ****
p = text;
do
{
! /* pend = strchr(p, '\r'); */
! pend = strchr(p, '\n');
if (pend == NULL)
pend = p+strlen(p);
--- 6028,6034 ----
p = text;
do
{
! pend = strchr(p, '\r');
if (pend == NULL)
pend = p+strlen(p);
|
Re: width of the textarea is too large (after reply), posted by Stefan Ritt on Fri Sep 5 17:17:03 2003
|
> The width of the textarea after pressing reply is too large.
> The problem is that the algorithm that searches for the longes line
> looks for the next '\r' which it does not find and therefore takes the
> number of characters in the text to be the width of the longest line.
> To search for '\n' instead should solve the problem. Please find the
> diff output below.
Ok, implemented, thanks. |
|
Re: problem with boolean attributes, posted by Stefan Ritt on Fri Sep 5 17:19:11 2003
|
> Boolean attributes were not displayed correctly in version 2.3.9.
> Patch is attached.
Yes, implemented, thank you. |
Currently being edited option has gone, posted by nickc1 on Thu Jul 10 10:11:41 2003
|
In the current source which ive compiled and am using on our elog system,
the feature that you put in for me that says "Entry is currently being
edited by Joe Bloggs on 192.168.0.10" has vanished.
It removes existing locks from before updating the binary but doesnt but
new ones on.
Is this something that was removed intentionally or by accident ?
Thanks |
|
Re: Currently being edited option has gone, posted by Stefan Ritt on Thu Jul 10 13:02:53 2003
|
> In the current source which ive compiled and am using on our elog system,
> the feature that you put in for me that says "Entry is currently being
> edited by Joe Bloggs on 192.168.0.10" has vanished.
>
> It removes existing locks from before updating the binary but doesnt but
> new ones on.
>
> Is this something that was removed intentionally or by accident ?
No, but there is now a flag "Use Lock = 0 | 1" which is zero by default,
since not all people want this feature. So put a "Use Locl = 1" and you
should be fine gain. |
|
Re: Currently being edited option has gone, posted by nickc1 on Fri Jul 11 11:09:10 2003
|
Excellent thanks |
Version 2.3.9 released today, posted by Stefan Ritt on Tue Jul 15 14:46:50 2003
|
Version 2.3.9 of elog has been released today. Enhancements are:
- Added options "Use Lock", "Title image"
- New "Email format" specifies what is sent exactly in an email
notification. This may now include also attachments
- "Format <attribute>" lets you assign separate style sheet classes to each
attribute, making the web display more powerful (see this forum,
the "subject" uses a separate formatting). Note that this feature requires
an update of the old "default.css" CSS file, if a elog version prior to
2.3.9 is already installed on a system.
- "Execute new/edit/delete" lets one execute shell commands on the server
side for new, edited or deleted messages. Since this can cause security
problems, a new flag "-x" has been added to the elogd daemon to enable this
feature. It can be used to synchronize the elog database with other
databases, or to send SMS messages to people.
- New "Logging level" option gives enhanced logging capabilities, including
read and write access logging to individual elog entries.
- The elog utility can now edit existing messages, and correctly quotes
messages with "> " on replies.
A few small bugs have been fixed, refer to the ChangeLog for more details. |