Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 251 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  68133   Tue Sep 29 08:50:30 2015 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportAll3.1.1Re: Creating ELog Links not working properly in HTML Editor
Hi Stefan,
yes, I know that a plain text "elog:1" works in the HTML editor, too.
But if you put "elog:1" in the URL field of the link dialog, then ELOG screws up: you get the text
and the link points to link type "URL", protocol "<other>", URL "1".
Or more precisely, the HTML source looks like the following:
   <a href="1">elog.1</a>&quot;&gt;<a href="1">elog.1</a>
(I've replaced ":" by "." here in the source, to avoid another iteration of links by ELOG).
That is not what I would have expected:
either it should have been remained unchanged, or it should point to the right URL of the entry elog:1 (the latter case preferred :-).
 
Cheers, Andreas
 
Stefan Ritt wrote:

Right, spaces won't work. But others work. Andreas, if you just put elog:1 without any link etc. just as plain text, it will be converted automatically into a link.

A workaround is to explicitly specify a link to an elog entry. Press the link button from the editor toolbar, enter a name and copy the full URL from the browser address bar, like here: https://midas.psi.ch/elogs/Forum/68129. If you switch to "Source" (Top left editor toolbar, you can changed the link name manually, like here.

Andreas Luedeke wrote:

I can confirm this bug.

But I don't think this has to work as you've described it, when using the HTML editor: if you use HTML, you can use the link feature of the editor.
But that link feature does currently not work at all with internal elog references, not even a simple elog:1">elog:1 (as you can see here). I suppose there is some more work to do for Stefan on that ;-)
 
Cheers, Andreas
Edmund Hertle wrote:

Hey,

the syntax for creating links to other elog entries has a small issue in the HTML editor. The link will not be created properly if there are whitespaces in the name of the logbook. Using ELCode (or in a simple attribute field) the whitespaces can be replaced by "+", but this does not work in the HTML editor. The work-around would be to use ELCode mark-up instead of HTML.

Example 1 (this should work): elog:Contributions/47

Example 2 (this will not work): elog:Config+Examples/11

Example 3 (will also not work): elog:Config%20Examples/11

 

 

 

  68144   Thu Oct 15 12:32:19 2015 Question kenzo Abrahamskenzoabrahams@gmail.comQuestionLinux3.1.1How does one create a html template for an entry
Good Day

I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.

Regard
Kenzo Abrahams
  68145   Thu Oct 15 14:34:36 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.1Re: How does one create a html template for an entry
> Good Day
> 
> I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
> a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
> or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.
> 
> Regard
> Kenzo Abrahams

So-called "custom" entry/view forms are a bit for experienced people. You should be fluent with HTML and JavaScript. The (minimal) documentation is here: https://midas.psi.ch/elogs/Forum/66909

If you want a table style input form, better use Google Spreadsheets.

Stefan
  68149   Mon Oct 26 11:06:46 2015 Question kenzo Abrahamskenzoabrahams@gmail.comQuestionLinux3.1.1Logging entries from the command line

Good Afternoon

Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is

elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile

I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.

Can anybody assist me please it would be much appreciated.

Regards

  68150   Mon Oct 26 11:16:54 2015 Reply kenzo Abrahamskenzoabrahams@gmail.comQuestionLinux3.1.1Re: How does one create a html template for an entry
> > Good Day
> > 
> > I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
> > a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
> > or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.
> > 
> > Regard
> > Kenzo Abrahams
> 
> So-called "custom" entry/view forms are a bit for experienced people. You should be fluent with HTML and JavaScript. The (minimal) documentation is here: https://midas.psi.ch/elogs/Forum/66909
> 
> If you want a table style input form, better use Google Spreadsheets.
> 
> Stefan

Thank you Stephan this really helped me.
  68151   Mon Oct 26 11:18:57 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.1Re: Logging entries from the command line

Run the elog command with an additional -v flag (verbose output), and you will see what the elogd server return. It's HTML, but you should be able to see some error message.

kenzo Abrahams wrote:

Good Afternoon

Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is

elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile

I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.

Can anybody assist me please it would be much appreciated.

Regards

 

  68152   Mon Oct 26 11:24:46 2015 Reply kenzo Abrahamskenzoabrahams@gmail.comQuestionLinux3.1.1Re: Logging entries from the command line

Hi Stephan

The error message I get is "Error: Command Submit not allowed". I dont know if this might be an issue but it says Response Recieved: HTTP/1.1 404 Not Found in the first line of the servers response

Stefan Ritt wrote:

Run the elog command with an additional -v flag (verbose output), and you will see what the elogd server return. It's HTML, but you should be able to see some error message.

kenzo Abrahams wrote:

Good Afternoon

Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is

elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile

I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.

Can anybody assist me please it would be much appreciated.

Regards

 

 

  68153   Mon Oct 26 11:32:08 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.1Re: Logging entries from the command line

This indicates that the username/password is not correct. Can you log in to that logbook in your browser with the username "John" and password "Blue"?

kenzo Abrahams wrote:

Hi Stephan

The error message I get is "Error: Command Submit not allowed". I dont know if this might be an issue but it says Response Recieved: HTTP/1.1 404 Not Found in the first line of the servers response

Stefan Ritt wrote:

Run the elog command with an additional -v flag (verbose output), and you will see what the elogd server return. It's HTML, but you should be able to see some error message.

kenzo Abrahams wrote:

Good Afternoon

Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is

elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile

I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.

Can anybody assist me please it would be much appreciated.

Regards

 

 

 

ELOG V3.1.5-3fb85fa6