Re: mySQL / SQL synchronisation, posted by rus on Wed Mar 28 04:05:01 2012
|
> does anybody has interest with a full synchronisation
> between elog logbook
> on mySQL and SQL database
I am interested!!!
But I don't know how to do that. |
|
Re: link to attachment within html editor, posted by Stefan Ritt on Mon Oct 9 12:30:44 2023
|
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)
|
|
|
Re: HTTP headers should be parsed case insensitive, posted by Stefan Ritt on Wed Jul 31 14:21:21 2024
|
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
| André wrote: |
|
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|
|
Re: 3.1.5 - Mass edit bug + Wrong version, posted by Stefan Ritt on Tue Feb 7 16:21:37 2023
|
I checked and found that the bug which removed the main text was there since the beginning, but it's only triggered if you switch elog to French, it doesn't happen in the English version. I changed a bit the text processing so now it should work also in the French version.
I also changed the version number which is shown at the bottom to 3.1.5.
Stefan |
|
Re: Wikipedia Article deleted, posted by Stefan Ritt on Thu Jan 19 17:00:37 2023
|
I agree. I ahead ;-) I think it is not a good idea if the ELOG author pushes on that, but better someone else.
Best,
Stefan
| Sebastian Schenk wrote: |
|
Hello,
I noticed the wikipedia article of the ELOG got deleted in November 2021.
With the reason: "Poorly sourced article, and I was not able to find good sources myself."
I could access the old article through web.archive.org, but for the project it would be good, if the article got revived.
|
|
|
Re: WYSIWYG Editor Not Showing in HTML Mode, posted by John on Mon May 5 11:47:11 2025
|
Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am
| Pawel Nita wrote: |
|
Hi all,
I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area.
Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!
Thanks in advance,
Pawel
|
|
|
Re: Parsing log files, posted by Lagarde on Wed Apr 7 17:11:28 2021
|
Hi,
I had similar needs (access and parse logs ) so I'm a small library in cpp. Have a look on https://github.com/flagarde/elogpp maybe it could be usefull for you too.
| Alan Grant wrote: |
|
Sometimes we change the attributes in a config file for a given tab as time goes on, which naturally can get out of sync with the older data in that tab.
I can imagine some other Elog users have encounterd this too at some point so I'm wondering if there's a utilty or some way anyone knows of that I can use to parse a log file DIRECTLY to view the older data, without using the Elog GUI?
|
|
|
Re: Extendable list of numeric items, posted by Nick Sauerwein on Mon Apr 8 17:23:00 2024
|
Hi John,
thanks for the info =). Do you known whether there is an example of how to use the list-boxes attributes?
Best,
Nick
| John Kelly wrote: |
|
Hi Nick,
If I understand your question correctly maybe this might help:
Search for 'attribute' and you will find this:
"some attributes may be pre-filled from system variables (like your user name). Pre-filled attributes may be still editable or read-only (like the entry creation date.
Attributes may be text fields (limited to 100 characters), list-boxes (max. 100 values), or check-boxes. There is also a special type of attribute where several values are listed on a line with check-boxes, and you can check as many values as needed."
I guess this above is like creating an attribute field, that has attribute names. I *thought* there was a way to leave attributes open where users could create their own 'attribute' names, but the information above is all of what I remember from my past in depth work with Elog.
John
| Nick Sauerwein wrote: |
|
Hey eloggers,
I am setting up an ELOG to log the cleanroom fabrication in our startup (Luxtelligence SA). The fabrication is structured in different process steps that are performed by several wafers at the same time (each wafer as an ID).
I am looking for an possibility to put a list of several integers as one of the attributes.
Here an example:
Attributes = Batch ID, Wafer IDs
Type Batch ID = numeric
Type Wafer IDs = extendable list of numeric values
Does something like this exsist?
Thanks in advance for your help.
|
|
|