I just found out that email notifications only worked for the first 50 users of this forum. So if you registered only recently, you might not have received any notification. This was a bug inside elogd which I hope to have fixed now (this entry notification will show...). If you get the first notification and do not want this, log in to the ELOG Forum, click on "Config" and remove the checkmarks from the logbooks you do not want to get notifications.

Hi,

is it possible to create a new column on the main page? Between "Logbuch" and "Einträge" I need the new column for enter the IP from the servers.

Thanks for your help

Markus

You can use the "Comment = ..." option to add something below "Logbuch" like I did here:

 Hi,

I use the "Comment=..." option to add the OS-Version. For a better overview it would be nice to add a new column for IP.

If this is not possible I use the "Comment...= option.

It is currently not possible to have a new column. But you can add some <br> tags inside your comment, then you IP will show up on a new line after the OS-Version. 

 This is Ok but in wich file can i add this tag? In the .cfg-file?

Yes, this goes into the elogd.cfg file. Just add a line like:

[logbook]

Comment = OS-Version<br><i>192.160.0.1</i>

Then you will get something like this:

 Thanks, this is great.

By, Markus

Hello,

please could you help me.

The Restrict edit funktion is not working. Because my user Dirk is able to edit/delete the text from user Peter:

 via select and edit.

Delete the - keep original text here - and then submit.

The whole text disappeared from the user Peter

I have tried both Restrict edit = 0 and then Restrict edit = 1 

Please note my config:

[global]
port = 80
Password file = C:\Program Files\ELOG\test.txt
Admin user = admin3
Self register = 1
Login expiration = 0

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Login user = Peter, Dirk, Kervin, Frank, MichaelH
Password file = C:\Program Files\ELOG\user.txt
Self register = 1
Login expiration = 0
Restrict edit = 0

Thanks

First, you need "Restrict edit = 1" in your config file. Then for each edit operation the system checks the currently logged in user against the "Author" attribute. Therefore, the "Author" attribute must contain the full user name. This can be achieved by adding

Preset Author = $long_name
Locked Attributes = Author

as described in the manual.

Hi

I was just wondering if there was a way that the comments for a logbook could be set to be invisible on the Selection page but then displayed once a user has logged in to a particular logbook?

This is required for security purposes. I want a common login page which shows all logbooks, where the logbook names only have meaning for people who know them but then once logged in the comment provides additional information about that logbook.

Thanks

Adam

Ok, I implemented a new option "Hide comments = 1" in SVN revision #2182, which will be included in the next release of elog.

Hello Stefan and Elog fans,

Is there a way to find entries with the words program and error when then are not contiguous in the text?

Thanks,
--Mike

Please have a look at

https://midas.psi.ch/elogs/Forum/66151

does this help? 

 Hello Stefan,

I am looking for the same answer that Yoichi was looking for.  For instance, could the text keyword filtering be looped so that the first group of results is then filtered by the next keyword?

--Mike

No, that's not possible unfortunately. 

Hi,

I want to write a text like "John:Doe" in ELCODE. However the ":D" is converted to a LOL emoticon. I tried various ways to escape this. One solution I found was entering "John\:Doe". However, the upper-case D is converted to lower-case: the result reads "John:doe".

Thanks for an answer and many thanks for providing ELOG.

Gernot

Thanks for reporting this bug. I fixed it in revision #2180.