| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69700
|
Mon Oct 9 12:30:44 2023 |
 | Stefan Ritt | I guesstefan.ritt@psi.ch | Question | Windows | ELOG V3.1.3-793 | Re: link to attachment within html editor |
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)
|
|
|
69701
|
Mon Oct 9 16:43:06 2023 |
 | Celeste Torkzaban | torkzaban at iqo.uni-hannover.de | Question | Windows | ELOG V3.1.3-793 | Re: 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)
|
|
|
|
69681
|
Mon Aug 14 08:35:58 2023 |
| Stefan Ritt | Therestefan.ritt@psi.ch | Question | Linux | 3.1.5-1 | Re: line breaks in 'Subject' |
There are two locations where 'Subject' is shown, the list display and the individual message display. I guess you mean the first one.
In that case, you can modify the CSS styel sheet 'elog.css' and add following statement to the classes list2 and list2h:
.list2 {
...
white-space: nowrap;
}
.list2h {
...
white-space: nowrap;
}
| Evinrude Motor wrote: |
|
Certain characters contained in the 'Subject' will cause the text to split into multiple lines .
For example if I enter "My Subject" in the 'Subject' field it is displayed as
My
Subject
If I enter "My_Subject" it is displayed as
My_Subject
Is there any way to change this so no line breaks are created ?
|
|
|
69682
|
Mon Aug 14 13:15:38 2023 |
| Evinrude Motor | minsonj2016@gmail.com | Question | Linux | 3.1.5-1 | Re: line breaks in 'Subject' |
Thanks for that bit of info . I had looked at that file but the answer was not obvious to me . Now I have to have an ELOG entry about , well , ELOG :}
| Stefan Ritt wrote: |
|
There are two locations where 'Subject' is shown, the list display and the individual message display. I guess you mean the first one.
In that case, you can modify the CSS styel sheet 'elog.css' and add following statement to the classes list2 and list2h:
.list2 {
...
white-space: nowrap;
}
.list2h {
...
white-space: nowrap;
}
| Evinrude Motor wrote: |
|
Certain characters contained in the 'Subject' will cause the text to split into multiple lines .
For example if I enter "My Subject" in the 'Subject' field it is displayed as
My
Subject
If I enter "My_Subject" it is displayed as
My_Subject
Is there any way to change this so no line breaks are created ?
|
|
|
|
966
|
Wed Mar 2 15:00:04 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: length of fields |
> When creating/updating entries in elog, excluding the main text field are
> there any limits on the size of the other fields?
Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
currently set to 1500 characters. You can try to increase this and recompile,
but at some point you will produce a stack overflow and elogd will crash. So
the current length is a compromise.
- Stefan |
|
969
|
Thu Mar 3 10:21:21 2005 |
| Paul Harrington | paul.harrington@oup.com | Question | All | | Re: length of fields |
> > When creating/updating entries in elog, excluding the main text field are
> > there any limits on the size of the other fields?
>
> Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> currently set to 1500 characters. You can try to increase this and recompile,
> but at some point you will produce a stack overflow and elogd will crash. So
> the current length is a compromise.
>
> - Stefan
Thanks. Thats useful to know.
Paul |
|
975
|
Tue Mar 8 13:16:14 2005 |
| Paul Harrington | paul.harrington@oup.com | Question | All | | Re: length of fields |
The reason for the earlier question is that we are trying to use Elog to store
data in a form we'd need to store more 1500 characters in more than one field.
Is it possible to get around this problem by having more then one main text field
per record?
thanks
Paul
> > > When creating/updating entries in elog, excluding the main text field are
> > > there any limits on the size of the other fields?
> >
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> >
> > - Stefan
>
> Thanks. Thats useful to know.
>
> Paul |
|
979
|
Tue Mar 8 20:28:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: length of fields |
> Is it possible to get around this problem by having more then one main text field
> per record?
No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so. |