| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
944
|
Mon Feb 14 19:03:31 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.5.7-1 | Re: Configuration problems |
> I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server. I started
> the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> server on that port, I get a 500 server configuration error. The Apache log
> contains this:
>
> malformed header from script. Bad header=Please specify hostname.: elog
- make sure your proxy definition in httpd.conf is correct and it uses port 8080
- start elogd with the "-v" flag to see the communication between Apache and elogd
- maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
file |
|
945
|
Mon Feb 14 20:39:30 2005 |
| Erich Beyrent | erich.beyrent@beyrent.net | Question | Other | 2.5.7-1 | Re: Configuration problems |
> > I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server. I started
> > the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> > server on that port, I get a 500 server configuration error. The Apache log
> > contains this:
> >
> > malformed header from script. Bad header=Please specify hostname.: elog
>
> - make sure your proxy definition in httpd.conf is correct and it uses port 8080
> - start elogd with the "-v" flag to see the communication between Apache and elogd
> - maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
> file
No luck. I have the proxy definition in my httpd.conf file. I have the URL parameter
in my elogd.cfg file.
Here is the command line I am using to start the daemon:
elogd -v -D -n <myhost> -p 8080 -l <myhost>/cgi-bin/elog/logbooks -c
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
With the -v argument, here are the messages I get in /var/log/messages:
elogd 2.5.7-1 built Feb 14 2005, 09:55:19
Feb 14 14:38:28 onion elogd[34579]: revision 1.558
Feb 14 14:38:28 onion elogd[34579]: Config file :
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
Feb 14 14:38:28 onion elogd[34579]: Resource dir : /usr/local/server/apache/cgi-bin/elog/
Feb 14 14:38:28 onion elogd[34579]: Logbook dir :
/usr/local/server/apache/cgi-bin/elog/logbooks/
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "elog"
Feb 14 14:38:28 onion elogd[34579]: Group "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "nogroup"
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "elog"
Feb 14 14:38:28 onion elogd[34579]: User "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "nobody"
Feb 14 14:38:28 onion elogd[34579]: Indexing logbook "demo" ...
Feb 14 14:38:28 onion elogd[34579]:
Feb 14 14:38:28 onion elogd[34579]: ID 1, 011108a.log, ofs 0, thead, MD5=
Feb 14 14:38:28 onion elogd[34579]: E4
Feb 14 14:38:28 onion elogd[34579]: 25
Feb 14 14:38:28 onion elogd[34579]: 4C
Feb 14 14:38:28 onion elogd[34579]: B8
Feb 14 14:38:28 onion elogd[34579]: AD
Feb 14 14:38:28 onion elogd[34579]: 4E
Feb 14 14:38:28 onion elogd[34579]: 88
Feb 14 14:38:28 onion elogd[34579]: 68
Feb 14 14:38:28 onion elogd[34579]: 08
Feb 14 14:38:28 onion elogd[34579]: 91
Feb 14 14:38:28 onion elogd[34579]: C9
Feb 14 14:38:28 onion elogd[34579]: 4D
Feb 14 14:38:28 onion elogd[34579]: 1E
Feb 14 14:38:28 onion elogd[34579]: B7
Feb 14 14:38:28 onion elogd[34579]: CB
Feb 14 14:38:28 onion elogd[34579]: C3
Feb 14 14:38:28 onion elogd[34579]:
Feb 14 14:38:28 onion elogd[34579]: After sort:
Feb 14 14:38:28 onion elogd[34579]: ID 1, 011108a.log, ofs 0
Feb 14 14:38:28 onion elogd[34579]: ok
Feb 14 14:38:28 onion elogd[34579]: Server listening on port 8080 ...
I am still getting the exact same error in my Apache log.
Any more ideas?
-Erich- |
|
946
|
Mon Feb 14 20:43:48 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.5.7-1 | Re: Configuration problems |
> No luck. I have the proxy definition in my httpd.conf file. I have the URL parameter
> in my elogd.cfg file.
Can you show me the proxy definition? I hope you don't treat elogd as a CGI script... |
|
65695
|
Fri Jan 11 08:08:51 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.0-1954 | Re: Configuration of HTML editor |
| Kristján Jónsson wrote: |
|
Do I have to do any extra configuration in elog to enable the FCKeditor.
What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).
ELCode works as expected. Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup. Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.
I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory. All are world readable.
Any hints about what could be the problem?
|
Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.
|
|
65696
|
Fri Jan 11 14:33:58 2008 |
| Kristján Jónsson | kj@raunvis.hi.is | Question | Linux | 2.7.0-1954 | Re: Configuration of HTML editor |
| Stefan Ritt wrote: |
|
| Kristján Jónsson wrote: |
|
Do I have to do any extra configuration in elog to enable the FCKeditor.
What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).
ELCode works as expected. Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup. Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.
I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory. All are world readable.
Any hints about what could be the problem?
|
Version 1954 is a bit old. Please update to the current SVN version and try again. There must be a file elog/scripts/fckeditor/fckeditor.js which was missing at some time.
|
Excellent, works as expected now, thanks.
Didn't realise how far behind the SVN version elog-latest.tar.gz is.
|
|
68707
|
Mon Nov 27 22:10:22 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | ELOG V3.1.3-fd7 | Re: Config: conditional coloring of items when 2 conditions are met (and|or) |
I am not aware that it is forseen to define logical operators in combination with the Style command. How did you get the idea that this should work?
But you should be able to define multiple Style commands, acting on different format parameter.
| Tim Schelfhout wrote: |
|
Hello,
Trying to color an entry log when 2 conditions are met. Tried
Style Result Hired and Administration NOK = background-color:red
where Result and Administration are Attributes. Anyone?
|
|
|
66321
|
Thu Apr 16 08:34:03 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.5 | Re: Config so that users can delete only their own entries? |
| Dennis Seitz wrote: | I've tried
Deny_Delete = All
Allow Delete = $author
and just
Allow Delete = $author
But either users can delete anyone's entries, or they can't delete any entries.
Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?
Thanks as usual for a great piece of code! |
You cannot put $author into any Allow or Deny option, only explicit login names (not "full" names). What you want however is
Restrict Edit = 1
which lets only the original author either delete or edit entries. If you use that option, you probably want as well
Preset Author = $long_name
Preset on reply Author = $long_name
Preset on duplicate Author = $long_name
Locked Attributes = Author
So a user cannot pretend to be somebody else. You also need a valid "admin user = ..." statement. Note that the admin user always can delete/edit entries. If no admin user is defined, everybody has automatically admin rights, so Restrict Edit has no effect. |
|
66323
|
Sat Apr 18 00:33:53 2009 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.5 | Re: Config so that users can delete only their own entries? |
Thanks for reminding me of that, it will do fine. A suggestion: Separate Restrict Edit into Restrict Edit and Restrict Delete or some functional equivalent. Then we have the choice to restrict one or the other or both. Is that worth doing?
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | I've tried
Deny_Delete = All
Allow Delete = $author
and just
Allow Delete = $author
But either users can delete anyone's entries, or they can't delete any entries.
Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?
Thanks as usual for a great piece of code! |
You cannot put $author into any Allow or Deny option, only explicit login names (not "full" names). What you want however is
Restrict Edit = 1
which lets only the original author either delete or edit entries. If you use that option, you probably want as well
Preset Author = $long_name
Preset on reply Author = $long_name
Preset on duplicate Author = $long_name
Locked Attributes = Author
So a user cannot pretend to be somebody else. You also need a valid "admin user = ..." statement. Note that the admin user always can delete/edit entries. If no admin user is defined, everybody has automatically admin rights, so Restrict Edit has no effect. |
|