> This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.

but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you 
find the right place, replace .innerHTML with current date?

K.O.

This was given to me by Andreas L, 

In my elog.cfg file, I have the following:

Preset text = $shell(date '+[%d %b %y]')\n

and this puts at the top of every new thread I make today the following line

[09 Apr 24]

And for the same result for every reply as well, I have in elog.cfg

Prepend on reply = $shell(date '+[%d %b %y]')\n\n----------\n

with the ten dash characters to show the end of the thread, so the reply entry goes above the dashes.

Obviously time, name of day etc can be included by using the strftime 


> > This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.
> 
> but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you 
> find the right place, replace .innerHTML with current date?
> 
> K.O.

This was given to me by Andreas Luedeke of this parish. 

In my elog.cfg file, I have the following:

Preset text = $shell(date '+[%d %b %y]')\n

and this puts at the top of every new thread I make today the following line

[09 Apr 24]

And for the same result for every reply as well, I have in elog.cfg

Prepend on reply = $shell(date '+[%d %b %y]')\n\n----------\n

with the ten dash characters to show the end of the thread, so the reply entry goes above the dashes.

Obviously time, name of day etc can be included by using the strftime codes.


> > This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.
> 
> but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you 
> find the right place, replace .innerHTML with current date?
> 
> K.O.

Thumbnail display in "full view" is implemented already. Let's take this entry: I insert a picture and scale it down via the "smaller" button:

Now if you display this forum in full view, the image is still shown as a thumbnail, which you are able to click in order to get the full resolution display. I don't know what is different in your case, maybe you are using an oder version of ELOG?

 Sorry for the delayed reply.

Ideally I'd like a config setting so that by default all graphics are presented at a fixed thumbnail size, so the users don't have to edit the image size every time they add one. Clicking on the thumbnail would open the image full size.

This would by default streamline loading and scanning through pages with many large images, whether in Full view of an entire logbook, or when viewing individual entries.

Have you tried Thumbnail size = xxx in your config file?

As an example, I created this same entry in the demo logbook using Safari.  As you can see there, the message is wrapped at the width that I set the text entry box.

https://elog.psi.ch/elogs/Linux+Demo/9

> When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.
> 
> For example, configure a logbook with:
> Message Width = 76
> Message Height = 20
> 
> Then, create a new plain text entry that contains very long lines.  The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly.  The summary display is wrapped properly, but not the full display.
> 
> We've only found this to be a problem with recent versions of firefox.  Chromium, Safari, and old versions of firefox behave properly.

[...]
> Probably it is fine to display only files ending in '.txt' per default.
> In addition a file that has more than say 1000 lines should probably 
> also not be displayed (as default, optional OK).  

No, '.txt' would definitely not be enough for me. I'm using elog to log all
administration of our network. In many cases, I simply attach a configuration
file. All those files are plain ASCII and none of them end in '.txt' - and I
would most definitely like them to be displayed inline like they are now. In
fact, this change was the main reason for me to upgrade to 2.5.4

Maybe a configuration option or a "display attachment" button would be the
best solution, then?

Cheerio,

Thomas