As the title says, we have our elog running behind an Apache proxy that is also providing authentication. We also have top groups enabled.  The first time a user views a top group page with a fresh browser cache, the index is delivered, but requests for elog.css and lock.png are returned with http 302 with location set to the elog root.  (I.e., if the server is proxied under server.example.com/logs,  the first request for server.example.com/logs/TopGroup1/elog.css returns a 302 with location set to server.example.com/logs// ). 

Any subsequent visits return the files fine. The attached screenshot shows the network requests in chrome. 

Is this a proxy configuration issue, something we've set wrong in elog, ??

We're running elogd behind an apache proxy server, with Authentication = Webserver. We have top groups configured, but a single shared password file.

If a user is looking at a particular logbook and goes to the Config link, they are presented with a list of checkboxes for email subscription to logbooks in that top group.  Clicking "Save" will remove all email subscriptions from all other top groups.

Is there a workaround to this issue?

EDIT: Manually adding an entry for different logbooks in the password file gets clobbered the next time the user logs in.

Hi everybody,

sorry if this question has already been posed (I did a quick search but I didn't found anything): elog sorts entry by ID, I wonder if it is possible to pin an entry in order to be always on top of the page independently on its ID.

Thanks

Giuseppe

This is not directly possible, but you can configure it with a trick. Create an attribute "pinned", make it of type "boolean", and set the start page such that it sorts using the "pinned" attribute:

Atributes = ..., Pinned
Options Pinned = boolean
Start page = ?rsort=Pinned

This move all entries where "Pinned" is true to the top of the list.

Stefan

How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?