ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69506
|
Sat Apr 16 10:37:24 2022 |
| Maarten de Jong | mjg@nikhef.nl | Question | Linux | 3.1.4 | Download attachments from command line |
Would it be possible to download attachments (e.g. with elog or wget) from the command line? |
69517
|
Thu Apr 21 14:19:35 2022 |
| Maarten de Jong | mjg@nikhef.nl | Question | Linux | 3.1.4 | Re: Download attachments from command line |
Thanks - I can confirm that the given command works.
However, for an e-log with username and password protection, this no longer seems to work.
It would be very useful if the elog command can be used to also download attachments (and not only a message).
Stefan Ritt wrote: |
Sure. Just figure out the URL from your browser and then use it in wget, e.g.
wget https://elog.psi.ch/elogs/Forum/220309_175728/elog-3.1.4-1ebfd06c-win64.zip
to download one attachement from this forum.
Stefan
Maarten de Jong wrote: |
Would it be possible to download attachments (e.g. with elog or wget) from the command line?
|
|
|
66736
|
Wed Mar 10 10:36:02 2010 |
| Mirza Ehsan | mirza@cpjeddah.com | Bug report | Windows | 2.6.1-1681 | eLog crash |
I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action.
I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.
If any one can help me in fixing this problem |
66758
|
Sat Mar 13 09:40:37 2010 |
| Mirza Ehsan | mirza@cpjeddah.com | Bug report | Windows | 2.6.1-1681 | Re: eLog crash |
Stefan Ritt wrote: |
Mirza Ehsan wrote: |
I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action.
I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.
If any one can help me in fixing this problem
|
I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts.
|
Thanks for the reply. I found problem with existing version. I opened log book group without opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.
Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery. |
66203
|
Wed Feb 11 16:32:42 2009 |
| ermirza erekose | mirza98@fastmail.net | Question | Linux | 2.7.5-2130 | Internal error, no valid header! |
I got this error message when trying to upload 17K text file as attachment. Any idea why ? It's a fresh installed elog and not much configuration done yet.
Thanks
|
66207
|
Fri Feb 13 03:58:46 2009 |
| ermirza erekose | mirza98@fastmail.net | Question | Linux | 2.7.5-2130 | Re: Internal error, no valid header! |
Stefan Ritt wrote: |
ermirza erekose wrote: |
I got this error message when trying to upload 17K text file as attachment. Any idea why ? It's a fresh installed elog and not much configuration done yet.
|
No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog?
|
No problem attaching big files on F10 or CentOS 4.7. The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-). All tested with ELOG version 2.7.5 build 2130.
|
66209
|
Sat Feb 14 17:49:59 2009 |
| ermirza erekose | mirza98@fastmail.net | Question | Linux | 2.7.5-2130 | Re: Internal error, no valid header! |
ermirza erekose wrote: |
Stefan Ritt wrote: |
ermirza erekose wrote: |
I got this error message when trying to upload 17K text file as attachment. Any idea why ? It's a fresh installed elog and not much configuration done yet.
|
No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog?
|
No problem attaching big files on F10 or CentOS 4.7. The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-). All tested with ELOG version 2.7.5 build 2130.
|
Correction. The OSes are OK. But don't use Opera when uploading big files. |
69680
|
Sun Aug 13 20:24:41 2023 |
| Evinrude Motor | minsonj2016@gmail.com | Question | Linux | 3.1.5-1 | line breaks in 'Subject' |
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 ? |