Re: Problem with a self-compiled code., posted by Maxim on Wed Jun 23 14:08:15 2021
|
Good afternoon Sebastian!
Thank you very much for your help.
| Sebastian Schenk wrote: |
|
Hello Maxim,
I just stumbled on a similar issue. Also with a self-compiled elogd on Ubuntu.
We also use a custom css and by clicking on the "New" or "Reply" or "Duplicate" the elog generates the entry editor.
On the first load of this page the link to the css file is sometimes corrupted by having some garbage characters in it.
<link rel="stylesheet" type="text/css" href="ƒŒüthemes/name.css">
I found the bug in the code and made a PR on the bitbucket. Here is the commit to fix it yourself.
https://bitbucket.org/merrx/elog/commits/cea193ded7161bb6d1f67725ca109d2d4341128a
Best wishes,
Sebastian
| Maxim wrote: |
|
Dear, sir! There is a problem with a configuration file.
The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev). After a compilation a reference to our own css-file was written in configuration file and css-file was included in a folder “themes/default” of the project.
The problem is that in running elog-3.1.4-1 (and upper versions) css-file name in a code of a page has some random symbols before file-name, for example: <link rel="stylesheet" type="text/css" href="ø9öÿeLogOUK.css">. It was found that the problem is resolved if a string “Password file=passwd” is deleted, but in this case it is impossible to set passwords to the users.
Here is an example of configuration file which is taken from the forum and just one string (CSS=elogOUK.css) has added to the code
____________________________________________________________________
What can be done to resolve this problem?
|
|
|
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:21:25 2015
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:23:27 2015
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
Re: Problem with a draft message, posted by Stefan Ritt on Tue Jun 9 19:35:28 2015
|
Just read what I wrote at elog:67983
| David Pilgram wrote: |
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
|
Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 20:26:00 2015
|
I missed or don't remember that post. My vote is replace "Back" with "Delete" - or "Abort"
| Stefan Ritt wrote: |
|
Just read what I wrote at elog:67983
| David Pilgram wrote: |
|
Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.
| David Pilgram wrote: |
|
Just to comment that I submitted the entry below by pressing the "Back" button!
| David Pilgram wrote: |
|
Hi Stefan,
I had started to write a completely different bug report, but then realised I had not checked a detail. I had written about one sentence. So I decided to abort the message, and hit the "back" button. Only I found that this had created a new entry in the elog listings. I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!
It doesn't seem to have created an email, though. And for the sake of all your users, I'd not want to experiment here on the matter too much!
|
|
|
|
|
|
Re: Problem with MOptions , posted by Stefan Ritt on Wed Feb 8 11:56:02 2006
|
| Ulrich Trüssel wrote: | After upgrading to 2.6.1-1 (actually donwgraded in case of this problem to 2.6.0) i was not longer able to selct more than one MOptions selection in my ELOGs. Only the first slected selection was acepted by ELOG. Ex:
MOptions Test = Aa, Bb, Cc, Dd, Ee, Ff, Gg
Selecting: Bb, Cc, Gg
Submitting the entry form, autoreturn to the overview of the even made entry, only Bb was taken.
Any Idea what's happen? Did I miss something changing in 2.6.1-1 or may this be a bug? Thanks for ideas?
Would loke to upgreade to 2.6.1. in case of the new forms for long MOptions, but need to selct more than one! |
That should work in 2.6.1-2 now. |
|
Re: Problem with Email Notification, posted by Stefan Ritt on Sat Mar 1 15:08:07 2008
|
| mike cianci wrote: |
|
Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
Your SMTP server does not accept the email send request from ELOG. That can have many reasons. Most systems are set up so that they do not accept SPAM. To do that, they do various checking of the sender address etc. Maybe you need an "Email from = mike2.cianci@comcast.net" in your config file to have a "real" sender address. Some more information you can get if you start elogd interactively in a DOS box with the "-v" flag, because then you will see all the debugging output of the communication between elogd and your SMTP server. |
Re: Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 12:39:41 2014
|
| Markus Grosse-Kock wrote: |
|
Hi,
we have a problem. After windows updates, the elog service doesn´t start:
What can we do?
Best regards,
Markus
|
After I uninstalled the software and reinstalled, the function is working again.
Thanks.
Best regards,
Markus |
|