Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 793 of 795  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject
  69701   Mon Oct 9 16:43:06 2023 Cool Celeste Torkzabantorkzaban at iqo.uni-hannover.deQuestionWindowsELOG V3.1.3-793Re: link to attachment within html editor

thank you!

Stefan Ritt wrote:

You can always insert the full link to the attachment like this one: https://elog.psi.ch/elogs/Forum/231009_104933/SCR14.PNG

But you can also use elog:69699/1 as shown here. Unfortunately you can do that only after the entry has been submitted, so you know the ID number of that entry. Once you have it, edit the entry and put it in.

Stefan

 

Celeste Torkzaban wrote:

Hello,
I like the ELcode feature that lets you easily make an internal link to an attachment in the same post. However, I wasn't able to get this to work in the html editor, even though it's possible to use the ELcode format to link to another post in the logbook. When I type in elog :/1 in the html editor (without the space) and submit (even with an attachment present), it weirdly gets changed and shows up as 61/1 in the submitted elog, without any hyperlink. As far as I know we're using the standard elog code and only modified css parameters. Is there another syntax to link to attachments in html?
Testing it out here: 69699/1  (elog :/1 without the space turned into 69699/1)

 

 

  69707   Thu Nov 2 11:38:36 2023 Question Leonardo Tacconileonardo.tacconi@unifi.itQuestionWindows3.1.3Restricting entries view by user

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

  69708   Thu Nov 2 11:46:42 2023 Reply Stefan RittNo, stefan.ritt@psi.chQuestionWindows3.1.3Re: Restricting entries view by user

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Leonardo Tacconi wrote:

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

 

  69712   Mon Jan 8 11:06:49 2024 Entry Dr Marta Divallmarta.divall@epfl.chQuestionWindowsELOG V3.1.3-a38Maximum number of attributes

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

  69713   Mon Jan 8 11:08:14 2024 Reply Stefan RittZou stefan.ritt@psi.chQuestionWindowsELOG V3.1.3-a38Re: Maximum number of attributes

You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.

Best,
Stefan

Dr Marta Divall wrote:

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

 

  69714   Mon Jan 8 11:42:08 2024 Reply Dr Marta Divallmarta.divall@epfl.chQuestionWindowsELOG V3.1.3-a38Re: Maximum number of attributes

Dear Stefan,

 Thansk for the super fast response! To keep the stability of the system we will look for a different solution then. 

Best,

Marta

Stefan Ritt wrote:

You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.

Best,
Stefan

Dr Marta Divall wrote:

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

 

 

  69715   Mon Jan 8 15:56:40 2024 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsELOG V3.1.3-a38Re: Maximum number of attributes

In my case, I had a number of attributes which had a varied prefix.  For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes.  Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile.  Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes.  In your case suffixes may be better, but I hope you get the point.

Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.

Dr Marta Divall wrote:

Dear Stefan,

 Thansk for the super fast response! To keep the stability of the system we will look for a different solution then. 

Best,

Marta

Stefan Ritt wrote:

You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.

Best,
Stefan

Dr Marta Divall wrote:

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

 

 

 

  69716   Mon Jan 8 16:18:45 2024 Reply Dr Marta Divallmarta.divall@epfl.chQuestionWindowsELOG V3.1.3-a38Re: Maximum number of attributes

To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome. 

David Pilgram wrote:

In my case, I had a number of attributes which had a varied prefix.  For example, "progressed" , which could have no prefix, or prefix "I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a number of attributes.  Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile.  Suitable change in the elog config file will also make this easy to follow in how the entries are shown in threaded or full display modes.  In your case suffixes may be better, but I hope you get the point.

Although I have done a (linux) recompile in the past, v2.9 something, 120 attributes seemed not to affect things.

Dr Marta Divall wrote:

Dear Stefan,

 Thansk for the super fast response! To keep the stability of the system we will look for a different solution then. 

Best,

Marta

Stefan Ritt wrote:

You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than 100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.

Best,
Stefan

Dr Marta Divall wrote:

The maximum number or attributes is 100.

Is it possible to increase this?

Thanks!

 

 

 

 

ELOG V3.1.5-fe60aaf