I think I know what the answer(s) will be already.. that I will need to address this in JS. I don't want each screen to run/show the same code, other than the ones I want to.  AND I do not want to have to create a custom form for each 'menu option' to achieve this (if possible).

Thanx,

John

In JS, you have access to the browser URL via window.location. So you can write conditional code depending on the actual elog command.

Stefan

Wow thanks again Stefan for your kind and prompt responses!!

John

Greetings!

We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.

Now, I have a need to place the value of an attribute of the latest log entry into a basic text file.  Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file.  However, I would like to be able to do this using the Windows service which is running in the background. 

Is there another way to write the value of an attribute into a separate file?  If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands?  For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.

In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).

I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).

Thanks!
Frank

Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.

Wow, having these color signal lamps really looke like a cute solution, made me laugh.

No, there is no other way than the Execute new thing. I have given up long time ago to use Windows services, because they are very hard to debug and very limited. So at our site everything runs under Linux.

Have you tried to specify the explicit path of your log file? Like Execute new = echo $Status > C:\Path\Last_status.log

Best,
Stefan

Well, there I was, eating Thanksgiving dinner, when suddenly, it hit me (no, not indigestion).  I can write a simple program that parses out the latest "Status" from the most recent logbook file -- a relatively easy task, since it's a text file.  This solution avoids having to execute a shell command at all.  GOOOOOOAAAAAAL!!!

As always, I appreciate all your help...can't thank you enough!

All the best,
Frank

I decided to rebuild elog 3.1.4 in Catalina (MacOS 10.15.1), XCode 11.2.1.  As in previous builds, I needed to add to the Makefile pointers to openssl:

CFLAGS += -I/usr/local/opt/openssl/include

LIBS += -L/usr/local/opt/openssl/lib

The make builds cleanly, no errors, no warnings.  After make/make install, elogd segfaults immediately.  I saw the same behavior with the version in gitlab.  I kept my (very) old build and was able to make install it without recompiling and it still works.

I'll crack out the debugger when I have a chance to get more information, but has anyone else seen this problem?  

The Makefile is kind of obsolete, I switched to CMake. So the Makefiel is mostly there as backup. To compile elog, do

elog$ mkdir build; cd build
elog/build$ cmake ..
elod/build$ make install

that should also find your openssl library, since CMake is more clever.

I personally have not yet switched to MacOS Catalina, since I have too many 32-bit programs running there and wait until all of these get updated. Only then I will be able to test elog under Catalina.

Stefan

Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes.

Hello, Is there any way to organize logbooks in some kind of tree with sublogbooks or just have a subdirectories in a logbook directory on the filesystem (treat it as a sublogbook if its name is different from 4 digits of year and pin above all the entries in a list) to structure entires a bit?

Just use groups as written in the manual: https://elog.psi.ch/elog/config.html#groups

Stefan

Hello, I read carefully the manual, but I didn't find a way to hide the logbooks in the logbook bar and in the initial logbook selection for which the user does not have the access. So, if a user1 does not have the access to a specific logbook, user1 is not able to see that logbook in the bar and neither in the initial logbook selection. How can I do this without using the top groups?

Hi Stefano,

Kind Regards, Andreas

Hi Andreas,

many thanks for your answer. I partially agree with you, because sometimes "for privacy" of my working group I don't want that other users (external users) know the existance of the other logbooks.

Do you think that will be implemented in future?

Best regards, Stefano

Well, Stefan would need to answer that. But if you are good with C-programming, you might implement it yourself?

There is a way to implement it; but it makes your installation a lot more complicated: you can have two ELOG servers. The first has all logbooks but requires authentification to read any. The second has only the public logbooks, and they are mirrored from the first.

Hi Stefano,

that's what top groups were made for. So make a top group for yourself, and nobody will be able to see them without having the proper URL. Hiding logbooks from the logbook selection page is not possible since when people bring up that page, they are not yet logged in, so elog does not know who is accessing the page (fortunatley no face recognition yet!). So if elog doe not know who looks at that page, logobook which a certain use has no access to cannot be hidden becuase the user is not known at that point.

Best regards,

Stefan

*** edit ***

I solved my problem by removing the guest options from the logbooks ('Guest menu commands' and 'Guest List Menu commands'), this forbids any unauthorised user to see the content of the concerned logbooks. This is what I needed.

***********
 

Dear Stefan,

I am currently configuring elog for a user platform that will run different unrelated experiments for unrelated research groups. As Stefano, I also would like that user only see the logbooks that they are allowed to edit; your answer was

Hiding logbooks from the logbook selection page is not possible since when people bring up that page, they are not yet logged in, so elog does not know who is accessing the page

However if I set Protect Selection page = 1 in [global] and force users to log in before accessing the logbook selection page, wouldn't elog know who looks at the page?

I would like to use top groups to separate administrative tasks from experimental projects and maintain an easy flow between the different logbooks within a top group for those users that can edit more than one logbook (e.g. the employees of the user platform).

Kindly,

marijn

Hello Elog Forum

There is i ELOG the function to edit multiple posts eg. to change the staus from "ongoing" to "finished" -> in danish translation "igangværende" and "afsluttet", see the attached pictures.

When I select multiple post and want to edit them to status "afsluttet" i get the "udklip_2.jpg" entry form and change only the status to "afsluttet" (Finished)

The result is a error informing that the attribut "gem oprindelige værdier" does not exist. As a test i changed the text in the translation file from "Keep origianl values = gem oprindelige værdier" to "Keep origianl values = Keep origianl values" but the result is the same error: Attribut Keep original values does not exist.

Is there a solution to this or is or is mutiple editing of post not allowed?

Kind Regards Finn

I use editing of multiple entries frequently and it works fine for me.

To understand your problem I would suggest that you try a minimal configuration. If you have a test logbook with just one or two fields and it still does not work, then post the config here that people can reproduce your problem - and hopefully find a fix.

Cheers, Andreas

Hello Andreas

OK, I did install a version of ELOG with a minimum of settings and the edit of multiple settings works fine. I've tracked the issue to "Locked Attributes = Bruger".

If one or more of the attributes are locked i get the error "Error: Attribute option - keep original values - not existing". I'm not trying to change the locked attribute, but it seems when one is locked multiple editing is not possible.

Is that intended to work this way?

Kind Regards Finn

Hi Finn,

Hello Andreas

Show Attributes Edit = xxx, limits the attributes shown when editing but when you submit you get the error

Error: Attribute Bruger not supplied.

Please go back and enter the Bruger field.

If I save instead of submitting it looks like it does change the attribute as intented in my test Elog system. Unfortunately i've disabled save with "Save drafts = 0" in my live system - to only use submit, and enabling drafts only causes other issues. My configuration is attached

Kind Regards Finn 

Hello Andres

Or maybe my reply was unclear :-), but i did use the "Show Attributes Edit" the way you meant to not show attribute BRUGER and when i do that i get:

Error: Attribute Bruger not supplied.

Please go back and enter the Bruger field

Kind Regards Finn

Trial and error - it seems like this combination does the trick:

Locked Attributes = Author

Fixed Attributes Edit = Author

Allows you to edit eg. status of multiple entries even if one attribute is locked

Kind Regards Finn

Hi, I have been trying for a long time to get my web server logs to record when someone accesses my Elog server. I've tried Apache2, Lighttpd, and others, all with no luck. Either the web servers complain that the port I have Elog on is in use, or I just don't get any readings. I need to see who is accessing my  Elog from the web, and I hope there is a way.

Thanks again for such a wonderful program,

John

Have you tried

Logfile = ...
Logging level = 3

Thanx soo much Stefan.. I feel so stupid for not looking at the admin guide more :( But you how us nerds are-- read the manul last!

John :)

Hi again everyone; a Sebastian suggested I use a reverse proxy to complete my need to have logs show up when someone 'lands' on my first entry page. I see that Elog will only start recording logs when someone has actually started to do some work.. like login, read a post, etc... but NOT when they first enter the login page or 'listings' pages. I have tried fowarding from my router (both lighty and Apache) but so for no good. I will also look into  a vhost option and shareing the same port (very difficult- if even possible)  to  solve my dilema.

John :)

Hi,
that Sebastian would be me. I replied to the first entry, as it was a draft (site reloaded incorretly...) and now I can't see the post anywhere. But this is off topic.

We have elog running on port 8000 and forward the traffic via Apache to it. Apache handles the SSL and other sites on the server.
All you need is a apache site configuration like the following. The parameter you want is CustomLog. (Have a look in the internet for options.)
I have also used nginx as webserver and know it can also handle this proxy setup.
If you use the following config, the elog config needs the URL attribute in the (global) config.

Best wishes,
Sebastian

<VirtualHost *:443> # change 443 to  80, if you don't use SSL
        ServerName your.server.name

        # delete the next 3 lines, if you don't use SSL
        SSLEngine on
        SSLCertificateFile /path/to/your/ssl.crt
        SSLCertificateKeyFile /path/to/your/ssl.key

        ProxyPreserveHost On
        ProxyPass / http://127.0.0.1:8000/
        ProxyPassReverse / http://127.0.0.1:8000/

        # Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/access.log combined
        ErrorLog ${APACHE_LOG_DIR}/error.log

</VirtualHost>

Thank you soo much Sebastian once again for helping me!! This is something that will help me very much in the future with other situations similiar!

John :)