Re: Wikipedia Article deleted, posted by Edmund Blomley on Mon Jan 23 21:21:56 2023
|
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
| Sebastian Schenk wrote: |
|
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
| Andreas Luedeke wrote: |
|
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
| Stefan Ritt wrote: |
|
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: Wikipedia Article deleted, posted by Edmund Blomley on Tue Jan 24 11:31:59 2023
|
If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else
| Stefan Ritt wrote: |
|
I added some more references, that's about all I can do. Not sure if that is enough.
Stefan
| Edmund Blomley wrote: |
|
It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG
| Sebastian Schenk wrote: |
|
I have requested an undeletion of the article. The article was deleted "PROD", which means that someone tagged it. And if noone removes the tag, it could be deleted.
I could revive the article. So in the future, One should have an eye on it and maybe update the current version of the software.
If there iy an paper on the elog, maybe it could be cited for more creditability.
| Andreas Luedeke wrote: |
|
It looks to me like only an author of an article can contradict a deletion. I did not find a single method to even comment on the deletion.
I am not an Wikipedia expert, can anyone suggest on how to push for the article to be restored? Or do we just write it again, until people stop deleting it?
| Stefan Ritt wrote: |
|
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.
|
|
|
|
|
|
|
Very long URLs in message list corrupt layout, posted by Ederag on Sun Mar 10 01:07:53 2019
|
First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.
When there is a very long URL in a message in "plain" encoding,
and this message is displayed in a list of messages,
a very long scrollbar appears at the bottom (same "scroll width" as the URL)
and some tabs and and dropdowns (filters) are unreachable without scrolling.
This does not happen if
- the message is displayed in single message page
- the message has a ELCode encoding
The exact version used is
0b9f7ed0 Merge branch 'develop'
There are no relevant instructions in elog.css for .messagelist,
and I did not find any obvious fix in the source code. |
|
Reply on item not allowed moving item to other logbook, posted by Eddy Berends on Mon Nov 9 11:50:05 2009
|
After I moved an item from one logbook to another one I cannot reply on this item anymore.
When the submit button is clicked it returns: Submit not allowed
This eLog server running Linux is sync'd with an server running Windows XP.
On the windows server the funcionality is working perfect(so no Submit is not allowed on a reply) |
|
Re: Compilation failure on Mac OSX 10.9, posted by Ed McNichol on Tue Jan 14 05:19:47 2014
|
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
| Stefan Ritt wrote: |
|
| A.G. Schubert wrote: |
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.
Best regards,
Stefan
|
Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74. I undid my changes to Makefile, tried to compile, but got the same errors.
I then pulled down elog and mxml with git, and these are working for me with no errors. Thanks!
|
SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon.
|
I too am having issues installing on Mac OS X 10.9.1. I changed CFLAGS in makefile to;
CFLAGS += -O3 -funroll-loops -fomit-frame-pointer -W -Wall -D_FORTIFY_SOURCE=0
I get many lines of errors like this when I run make;
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/openssl/ssl.h:1491:6: note: 'SSL_accept' declared here
int SSL_accept(SSL *ssl) DEPRECATED_IN_MAC_OS_X_VERSION_10_7_AND_LATER;
^
src/elogd.c:28809:19: warning: 'SSL_set_fd' is deprecated: first deprecated in OS X 10.7 [-Wdeprecated-declarations]
SSL_set_fd(ka_ssl_con[i_min], ka_sock[i_min]);
^
|
Adding texts for each attachment, posted by Dongwook Jang on Mon Mar 16 22:33:23 2009
|
Dear Stefan,
First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.
I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.
I am not sure if someone was already suggested this or it is already in your wish list.
Thank you.
Dongwook Jang |
|
Re: Adding texts for each attachment, posted by Dongwook Jang on Tue Mar 17 02:05:08 2009
|
| Stefan Ritt wrote: |
|
| Dongwook Jang wrote: |
|
Dear Stefan,
First of all, I appreciate that you made such a nice program. I've used elog for more than 5 years and it was wonderful experince to me and my research work was very productive with this.
I have a suggestion to you to improve this while I was using elog. If users can add texts or comments for each attachment, it will be great.
I am not sure if someone was already suggested this or it is already in your wish list.
Thank you.
Dongwook Jang
|
Dear Dongwook,
no, this is not implemented and also was never requested. The way most people work is that images are included directly in the text, and the the text goes along with that.
So for example if I want to show you the ELOG logo, I put it here: 
If I want to add a comment for an attachment, I write it in the text and just refence the attachment with link. This way is more flexible that adding just a line of text to each attachment, since you can write several lines in the text, make a table etc. etc.
|
Dear Stefan,
Maybe I used elog with very inefficient way so far. The way you suggested requires putting figures somewhere else, right?
Elog saves attachments on the machine that elog is running. I want to store figures in elog.
The logo you showed above is stored in this entry?
Thank you.
Dongwook Jang |
elogd runs by a user but not by root, posted by Dongwook Jang on Tue Apr 28 21:25:31 2009
|
Hi,
I really don't understand why elogd cannot run by root but it runs by a user.
I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively.
Thanks,
Dongwook |
|