Re: Enhanced "eLog Version" Variable, posted by Steve Jones on Wed Oct 6 06:14:36 2004
|
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!
> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
>
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
>
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant? I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> >
> > EX:
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> >
> > Just a thought.
> >
> > Thanks |
Re: Enabling SSL, posted by Stefan Ritt on Tue Jun 5 12:28:27 2018
|
This comes from the openSSL library which elog includes. I tried myelf and found that a chained certificate is not correctly interpreted by the openSSL library. Most people anyhow don't use SSL inside elog, but run an Apache server in front of elog. This is anyhow better since Apache has an industry-strength security with regular updates. Much better than relying on OpenSSL.
Stefan
| Pasti wrote: |
|
Hi all,
I'm following config guide and so far so good. The only issue I run into is when enabling SSL.
Guide says - One can replace this certificate and key with a real certificate to avoid browser pop-up windows warning about the self-signed certificate.
Can you please tell me a more details regards this part? I have acquired security certificate and replaced contents of SSL folder.
Now elogd.exe gets error 1067.
Any help would be highly appreciated.
Thanks!
|
|
|
Re: Enable user to view only, not post/delete., posted by Stefan Ritt on Wed Jul 21 12:33:39 2010
|
| Denis Perevalov wrote: |
|
I have a question. Is there a way to enable user to view only, not post/delete in my elog. Also I would like to allow them to view only certain categories of my messages.
|
The first thing you can do with "Guest menu commands", where you enable only those commands which can't change or delete entries. The second thing you can only do if you put your entries into two separate logbooks, a public and a private one. |
|
Re: Empty mxml directory in commit a6e5962, posted by Stefan Ritt on Tue Jan 31 21:29:05 2017
|
The mxml package has been converted into a submodule in the git repository. At http://midas.psi.ch/elog/download.html you see that you need a "--recursive" flag to clone it. If you have already checked out the sources, you need a
git submodule update --init --recursive
/Stefan
| Christine Quicot wrote: |
|
Hello,
I wonder if it's normal that in the sources files, new created mxml directory is empty.
In commit # a6e5962 4 files are deleted but not moved:
- src/mxml.c
- src/mxml.h
- src/strlcpy.c
- src/strlcpy.h
Thank you
|
|
|
Re: Embedded images break when moving from one book to another., posted by Stefan Ritt on Thu Jun 4 15:37:44 2009
|
| Mike wrote: |
|
Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a
particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails
be displayed for each product. This works fine but when we move one message to another logbook the thumbnails
end up getting broken and won't be displayed. The only way to fix this is to remove the image and re-upload the
picture after the message is moved. This is not a good option because we have hundrends of items that are
constantly being moved around from logbook to logbook. Any ideas?
Regards,
Mike
EDIT:
On further inspection it seems that when you are moving messages to another log book the image date filename
is re-written which of course breaks the html link to the image. Is there anyway to supress this so that the filename
stays in tact when it's moved from one book to another. I don't see why the name of an attachment has to get changed
just because something is moved around.
|
I fixed this in revision #2204. The attachment names now stay the same. There is one tiny risk of screwing up, namely if you have the same attachment name in two different logbooks (accidentally also submitted at the same second and therefore the same time stamp). If you then copy these two entries to a third logbook, one attachment will overwrite the other one, but that risk is indeed really small. I actually had to re-write the link to the attachment inside the text body (even differently for ELCode and HTML encoding). So I'm not 100% sure I covered all cases, so just give it a try. |
|
Re: Embedded images break when moving from one book to another., posted by Mike on Thu Jun 4 17:51:02 2009
|
| Stefan Ritt wrote: |
|
| Mike wrote: |
|
Here's the issue. We use elog to develope products we need to be able to see all the thumbnail images in a
particular logbook. Our default view is to use the threaded view fully expanded in order to have all the thumbnails
be displayed for each product. This works fine but when we move one message to another logbook the thumbnails
end up getting broken and won't be displayed. The only way to fix this is to remove the image and re-upload the
picture after the message is moved. This is not a good option because we have hundrends of items that are
constantly being moved around from logbook to logbook. Any ideas?
Regards,
Mike
EDIT:
On further inspection it seems that when you are moving messages to another log book the image date filename
is re-written which of course breaks the html link to the image. Is there anyway to supress this so that the filename
stays in tact when it's moved from one book to another. I don't see why the name of an attachment has to get changed
just because something is moved around.
|
I fixed this in revision #2204. The attachment names now stay the same. There is one tiny risk of screwing up, namely if you have the same attachment name in two different logbooks (accidentally also submitted at the same second and therefore the same time stamp). If you then copy these two entries to a third logbook, one attachment will overwrite the other one, but that risk is indeed really small. I actually had to re-write the link to the attachment inside the text body (even differently for ELCode and HTML encoding). So I'm not 100% sure I covered all cases, so just give it a try.
|
This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?
Thanks Stefan!
Mike |
|
Re: Embedded images break when moving from one book to another., posted by Stefan Ritt on Fri Jun 5 12:42:55 2009
|
| Mike wrote: |
|
This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?
Thanks Stefan!
Mike
|
Can you try revision #2206?
|
|
Re: Embedded images break when moving from one book to another., posted by Mike on Fri Jun 5 14:13:52 2009
|
| Stefan Ritt wrote: |
| Mike wrote: |
|
This is a major improvement. The only issue now is when we embed an image in the body of the message elog makes a nice thumbnail. When you move the message to another logbook the thumbnail doesn't work and instead it shows the MASSIVE full size version of the picture instead. Is that possible to fix?
Thanks Stefan!
Mike
|
Can you try revision #2206?
|
Stefan,
Works perfectly, thanks for the fix you rock!
Mike |