Hi,

I've been exploring elog. I find when using IE 11, the text editor formatting buttons don't work with HTML encoding selected. The entire toolbar is grayed out. It appears to work fine with Chrome. Any ideas or direction to look? elog v3.1.1 is running on RedHat EL5. I've tried the rpm installation, and source code compilation and installation with no change.

Any input would be greatly apriciated!

John

Thanks for the quick response!

It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.

The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.

Thanks for the quick response!

The idea is to run multiple instances of elog where

That's strange. If you use HTML or ELCode encoding, attachments are automatically hidden if they are used inline. So no "Show attachments = 0" necessary! I just tried that with the demo logbook and here is how it looks:

As you can see, there is no attachment shown in the full view. This is actually handled by the function "is_inline_attachment()" in elogd.c. I don't know if you can do debugging, but somehow this inline test won't work for you and the question is why. Can you try the simple configuration from the demo logbook and see if you still have the problem? Can you show me an example when this does not work. I need to reproduce your problem exactly in order to fix it.

Stefan

I have "Show attachments = 0" set in [global], but attachments are shown in the "Full" view. Is this the intended behavior? Looking at individual entries correctly hides the attachments. 

We use inline images often, so when an attachement is shown at the bottom of a post it is effectively a duplicate, which clutters things up a bit. 

I guess the underlying problem is the long time these requests take and block other users.

I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.

Hello all,

I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.

Does anybody have any suggestions?

Regards,

Philip

Do you have the problem on this Forum as well?

If not, then something is wrong with your installation. Like old JavaScipt files etc. Start with a fresh installation and you should be fine.

If you have the same problem in this Forum, let me know and I will further investigate it.