This is another piece of information to help in the debugging. To my standards logbooks, I have added the "demo". On the demo I can upload pictures while I can't on the other logbooks.

This is indicating that the bug has something to do with the logbook configuration other than with the editor or the image upload plugin.

Thanks for your help,

Antonio

You can manually highlight code, but there is no automatic language parser.

I thought so.

One  more question :) I want manually add that parser (https://highlightjs.org), but I'm newby in that and don't know where ....

I know that downloaded hightlight pack I must put into folder scripts, but where to add this line:

<script>hljs.initHighlightingOnLoad();</script>

I did not know about highlight.js . You can put it into any elog page with "Bottom text = ...". I tried it for this forum and put in some C code:

#include <stdio.h>
int main()
{
   // printf() displays the string inside quotation
   printf("C Programming");
   return 0;
}

Seems like this works nicely. Thanks for that hint.

Looks like it works :)

Code need to be put in tags:

<pre><code class="sql">...</code></pre>

but it works.

Thank you :D

Best Regards

Daniel Sajdyk

#include <stdio.h>
int main()
{
   // printf() displays the string inside quotation
   printf("C Programming");
   return 0;
}

In the HTML editor, you can select the code text, then select from the "Styles" drop-down the style "Computer Code", and on the "Normal" drop-down the formatting "Formatted". This puts the code in <pre>  and <code> tags, so you don't have to manipulate HTML directly.

#include <stdio.h>
int main()
{
   // printf() displays the string inside quotation
   printf("C Programming");
   return 0;
}

Well, 5 years after opening this issue, with no responses here, I finally got into the source code and fixed it.

The problem seems to be if eLog is configured to prohibit users (non-administrators) from the "Config" option...but on the initial self-registration, the code goes to the Config screen for the user anyway...resulting in the false error message.

So, I [badly] hacked eLog to fix that, add some debugging/log messages, and to correct a typo.

Attached is the patch against release 3.1.1-1. Try not to cringe too much at my code. :)

Ok. Thanks a lot :)

#include <stdio.h>
int main()
{
   // printf() displays the string inside quotation
   printf("C Programming");
   return 0;
}